CVE-2022-47551

Description

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.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.26%
Vendor Advisory apiman.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://www.github.com/apiman/apiman third party advisory
https://www.apiman.io/blog/permissions-bypass-disclosure/ vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-47551?
CVE-2022-47551 has been scored as a medium severity vulnerability.
How to fix CVE-2022-47551?
To fix CVE-2022-47551, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-47551 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-47551 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.