Skip to content

Event search API returns all listed events without checking if the user has read access

Moderate
LukasKalbertodt published GHSA-f9jh-r227-r9qg Oct 25, 2023

Package

tobira (Released binary)

Affected versions

<= 2.2

Patched versions

2.3

Description

Impact

The API searchAllEvents, which is used in the video-block editor, can return any listed event, even when the current user has no read access to said event. This allows users to obtain metadata and the thumbnail URL of events they should not be able to see. The video or subtitle tracks are not exposed, and neither is the Opencast ID. So to the best of my knowledge, users are not able to watch the actual video.

Note: this is not the API that is used for the main search. The main site search performs the "read access" check correctly.

As a reminder: an event is listed if its series or any events in that series are included on a public page somewhere (i.e. not user pages). And since only listed videos are exposed by this bug, it's rather unlikely that very sensitive/private videos are exposed.

You can check if any of your videos are potentially affected by running tobira db console and then executing:

select title from search_events where not 'ROLE_ANONYMOUS' = any(read_roles) and array_length(host_realms, 1) > 0

This shows all non-public events that are listed. The metadata and thumbnail of those events can be accessed by anyone.

Patches

Patched in v2.3 and later.

Workarounds

You can make affected events (see query above) unlisted by removing their inclusion on pages.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses

No CWEs