WaratekVRT Sign in

CVE-2023-28640 Apiman

Affected softwareApiman
Severity6.4 Medium CVSS 3.1 2 scores
Fixed in3.1.0.Final
WeaknessImproper privilege management (CWE-269)
Published27 Mar 2023
Updated17 Jun 2026

Description

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.

CWE-862 · Missing authorizationCWE-280

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 3 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.34% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.
Candidate fix https://github.com/apiman/apiman/security/advisories/GHSA-m6f8-hjrv-mw5f : the maintainers' own security advisory: names the version that fixes it, so the fix is the difference between two releases

CVSS

6.4 MEDIUM v3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 6.4 MEDIUM CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N security-advisories@github.com Secondary published
CVSS 3.1 3.1 LOW CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
io.apiman:apiman-manager-api-rest-impl 0 3.1.0.Final unbounded

Products and versions

2 products, 2 version entries
SourceVendorProductSchemeAffected versions
nvd apiman apiman generic 3.0.0
osv io.apiman apiman-manager-api-rest-impl generic < 3.1.0

References

URLTags
https://github.com/apiman/apiman/security/advisories/GHSA-m6f8-hjrv-mw5f advisory
https://github.com/apiman/apiman PACKAGE
https://www.apiman.io/blog/potential-permissions-bypass-disclosure WEB
https://www.apiman.io/blog/potential-permissions-bypass-disclosure/ Mitigation, Vendor Advisory

Timeline

Published2023-03-27By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.