Skip to content

Apiman vulnerable to permissions bypass due to missing check on API key URL

Moderate severity GitHub Reviewed Published Mar 27, 2023 in apiman/apiman • Updated Apr 3, 2023

Package

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

Affected versions

< 3.0.0.Final

Patched versions

3.1.0.Final

Description

Impact

Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL. The URL includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource, and each of these can have arbitrary values.

While not trivial to exploit, it could be achieved by brute-forcing or guessing common names.

Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security).

Patches

Apiman 3.1.0.Final and later resolves this issue.

Workarounds

Only provide Apiman Manager accounts to known users, do not allow anonymous/unknown users to create an Apiman Manager account.

Note that this does not affect the Apiman Gateway.

References

References

@msavy msavy published to apiman/apiman Mar 27, 2023
Published by the National Vulnerability Database Mar 27, 2023
Published to the GitHub Advisory Database Mar 27, 2023
Reviewed Mar 27, 2023
Last updated Apr 3, 2023

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
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:C/C:L/I:L/A:N

EPSS score

0.054%
(24th percentile)

CVE ID

CVE-2023-28640

GHSA ID

GHSA-m6f8-hjrv-mw5f

Source code

Credits

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