CVE-2022-47551
Apache Apiman Unauthorized Read Permission Exposure
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.
INFO
Published Date :
Dec. 20, 2022, 12:15 a.m.
Last Modified :
Dec. 27, 2022, 6:38 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
2.8
Public PoC/Exploit Available at Github
CVE-2022-47551 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-47551.
| URL | Resource |
|---|---|
| https://www.apiman.io/blog/permissions-bypass-disclosure/ | Vendor Advisory |
| https://www.github.com/apiman/apiman | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
This is a list of artifacts from the GitHub Advisory Database where the corresponding JSON files are missing CVE identifiers, despite the fact that these artifacts are listed in the NVD (National Vulnerability Database). I cross-referenced the data, retrieved the missing CVEs, and compiled everything into a list.
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-47551 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-47551 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Dec. 27, 2022
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Changed Reference Type https://www.apiman.io/blog/permissions-bypass-disclosure/ No Types Assigned https://www.apiman.io/blog/permissions-bypass-disclosure/ Vendor Advisory Changed Reference Type https://www.github.com/apiman/apiman No Types Assigned https://www.github.com/apiman/apiman Third Party Advisory Added CWE NIST CWE-276 Added CPE Configuration OR *cpe:2.3:a:apiman:apiman:*:*:*:*:*:*:*:* versions from (including) 1.5.7 up to (including) 2.2.3
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-47551 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-47551
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.06 }} 0.00%
score
0.28700
percentile