Vulnerability in Apiman
CVE-2022-47551
Apiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. 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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.006 (47.8th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 48th percentile — 47.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.006 · newest: 0.006 · change: +0.000
Affected products
Weakness classification (CWE)
Public proof-of-concept exploits
References
- www.github.com/apiman/apiman (Third Party Advisory)
- www.apiman.io/blog/permissions-bypass-disclosure/ (Vendor Advisory)
Frequently asked questions
- What is CVE-2022-47551?
- CVE-2022-47551 is a medium-severity vulnerability in Apiman, classified under Incorrect Default Permissions. CVSS score: 6.5/10. Published 2022-12-20.
- How severe is CVE-2022-47551?
- Medium severity. CVSS v3 base score is 6.5 out of 10.
- Is CVE-2022-47551 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.