Permissions bypass in Apiman could enable authenticated attacker to unpermitted API Key

published 2023-03-27 3 y ago modified 2026-09-10 1 mo ago also GHSA-m6f8-hjrv-mw5f , EUVD-2023-1056

cvss: 6.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits: 0; none known

Apiman is a flexible and open source API Management platform. 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, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. 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). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.

Patch / fix

fixed in 1

maven io.apiman:apiman-manager-api-rest-impl 3.1.0.Final

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 20 mo ago (2025-02-19)

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD	3.1	3.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	6.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	io.apiman:apiman-manager-api-rest-impl	<3.1.0.Final	3.1.0.Final

Affected products

apiman apiman

Classification

Weakness

CWE-269 Improper Privilege Management
CWE-862 Missing Authorization
CWE-280 Improper Handling of Insufficient Permissions or Privileges

References

github.com /apiman/apiman/security/advisories/GHSA-m6f8-hjrv-mw5f
web, vendor-advisory
apiman.io /blog/potential-permissions-bypass-disclosure/
mitigation, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2023-28640
advisory
github.com /apiman/apiman
package
apiman.io /blog/potential-permissions-bypass-disclosure
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary