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.

CVSS v3 6.5 MEDIUM

6.5^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 2.8 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://www.apiman.io/blog/permissions-bypass-disclosure/	Vendor Advisory
https://www.github.com/apiman/apiman	Third Party Advisory
https://www.apiman.io/blog/permissions-bypass-disclosure/	Vendor Advisory
https://www.github.com/apiman/apiman	Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:apiman:apiman:*:*:*:*:*:*:*:*

History

21 Nov 2024, 07:32

Type	Values Removed	Values Added
References	~~() https://www.apiman.io/blog/permissions-bypass-disclosure/ - Vendor Advisory~~	() https://www.apiman.io/blog/permissions-bypass-disclosure/ - Vendor Advisory
References	~~() https://www.github.com/apiman/apiman - Third Party Advisory~~	() https://www.github.com/apiman/apiman - Third Party Advisory

Information

Published : 2022-12-20 00:15

Updated : 2025-04-17 15:15

NVD link : CVE-2022-47551

Mitre link : CVE-2022-47551

CVE.ORG link : CVE-2022-47551

JSON object : View

Products Affected

apiman

apiman

CWE

CWE-276

Incorrect Default Permissions

{"id": "CVE-2022-47551", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.8}, {"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "published": "2022-12-20T00:15:10.050", "references": [{"url": "https://www.apiman.io/blog/permissions-bypass-disclosure/", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.github.com/apiman/apiman", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.apiman.io/blog/permissions-bypass-disclosure/", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.github.com/apiman/apiman", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-276"}]}, {"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-276"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Apiman 1.5.7 a 2.2.3.Final no tiene comprobaciones suficientes para los permisos de lectura dentro de la API REST de Apiman Manager. La causa principal del problema es la aceptaci\u00f3n accidental por parte del proyecto Apiman de una gran contribuci\u00f3n que no era totalmente compatible con el modelo de seguridad de las versiones de Apiman anteriores a 3.0.0.Final. Debido a esto, 3.0.0.Final no se ve afectado por la vulnerabilidad."}], "lastModified": "2025-04-17T15:15:53.467", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apiman:apiman:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "A23860E0-A9F2-4F57-A4FC-4655ECBAA932", "versionEndIncluding": "2.2.3", "versionStartIncluding": "1.5.7"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}