Skip to content

Duplicate Advisory: Apiman has insufficient checks for read permissions

High severity GitHub Reviewed Published Dec 20, 2022 to the GitHub Advisory Database • Updated Oct 7, 2024
Withdrawn This advisory was withdrawn on Oct 7, 2024

Package

maven io.apiman:apiman-manager-api-rest-impl (Maven)

Affected versions

>= 1.5.7, <= 2.2.3.Final

Patched versions

3.0.0.Final

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-j94p-hv25-rm5g. This link is maintained to preserve external references.

Original Description

Apiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. A malicious user may be able to find and subscribe to private APIs they do not have permission for, thus accessing API Management-protected resources they should not be allowed to access. The root cause of the issue is the Apiman project's accidental acceptance of a large contribution that was not fully compatible with the security model of Apiman versions before 3.0.0.Final. Because of this, 3.0.0.Final is not affected by the vulnerability.

References

Published by the National Vulnerability Database Dec 20, 2022
Published to the GitHub Advisory Database Dec 20, 2022
Reviewed Dec 20, 2022
Last updated Oct 7, 2024
Withdrawn Oct 7, 2024

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
None
Scope
Unchanged
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:N/S:U/C:H/I:L/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-54r5-wr8x-x5v3

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.