Skip to content

Unauthenticated Access Via OAI-PMH

High severity GitHub Reviewed Published Jan 29, 2020 in opencast/opencast • Updated Jan 9, 2023

Package

maven org.opencastproject:opencast-oaipmh-api (Maven)

Affected versions

< 7.6
>= 8.0, < 8.1

Patched versions

7.6
8.1

Description

Impact

Media publication via OAI-PMH allows unauthenticated public access to all media and metadata by default. OAI-PMH is part of the default workflow and is activated by default, requiring active user intervention of users to protect media. This leads to users unknowingly handing out public access to events without their knowledge.

Patches

The problem has been addressed in Opencast 7.6 and 8.1 where the OAI-PMH endpoint is configured to require users with ROLE_ADMIN by default. In addition to this, Opencast 9 removes the OAI-PMH publication from the default workflow, making the publication a conscious decision users have to make by updating their workflows.

Workarounds

In the organization security configuration (etc/security/mh_default_org.xml), change the roles required for accessing /oaipmh from ROLE_ANONYMOUS to ROLE_ADMIN.

References

For more information

If you have any questions or comments about this advisory:

References

@lkiesow lkiesow published to opencast/opencast Jan 29, 2020
Reviewed Jan 30, 2020
Published to the GitHub Advisory Database Jan 30, 2020
Last updated Jan 9, 2023

Severity

High

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
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:L/UI:R/S:C/C:H/I:L/A:N

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2020-5228

GHSA ID

GHSA-6f54-3qr9-pjgj

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.