CVE-2022-47551: Apiman manager api rest impl Apiman Has Potential Permissions Bypass Vulnerability
HIGHCVE-2022-47551 is a HIGH (CVSS 7.1) apiman has potential permissions bypass vulnerability (General Security Weakness) affecting Apiman manager api rest impl libraries in the Maven ecosystem. The issue involves apiman has potential permissions bypass. Remediation is available by upgrading affected packages to version 3.0.0.Final.
CVE-2022-47551 at a Glance
Security Impact
CVSS: 7.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).
How to Fix CVE-2022-47551
To remediate this vulnerability, upgrade all affected Apiman manager api rest impl dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>io.apiman</groupId>
<artifactId>apiman-manager-api-rest-impl</artifactId>
<version>3.0.0.Final</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=io.apimanHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2022-47551, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.apimanAnalyze the terminal output to locate any version of Apiman manager api rest impl in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.0.Final), your application is affected.
Note: The mvn dependency:tree -Dincludes=io.apiman command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In Apiman manager api rest impl, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-47551 Affected Apiman manager api rest impl Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
io.apiman:apiman-manager-api-rest-impl
|
Maven |
≥ 1.5.7
< 3.0.0.Final
|
3.0.0.Final
|
References
Frequently Asked Questions
What is CVE-2022-47551?
Which Apiman manager api rest impl versions are affected?
What version fixes CVE-2022-47551?
Is apiman-manager-api-rest-impl affected?
What is the CVSS score of CVE-2022-47551?
What CWE is associated with CVE-2022-47551?
How can I check Maven dependencies for CVE-2022-47551?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-j94p-hv25-rm5g",
"modified" : "2023-01-03T12:28:06Z",
"published" : "2023-01-03T12:28:06Z",
"aliases" : [ "CVE-2022-47551" ],
"summary" : "Apiman has potential permissions bypass",
"details" : "### Impact\n\nIncorrect default permissions for certain read-only resources in the Apiman 1.5.7.Final through 2.2.3.Final in the Apiman Manager REST API allows a remote authenticated attacker to access information and resources in an Apiman Organizations they are not a member of and/or do not have permissions for.\n\nFor example, an attacker may be able to craft an HTTP request to discover APIs that are private to organizations they are not members of, via fuzzing, search, and other similar mechanisms.\n\nIf the attacker has sufficient permissions in their own organization, they may also be able to sign up to the private APIs they have discovered by crafting a tailored HTTP request, thereby gaining access to an API Management protected resource that they should have access to.\n\n* A malicious account-holder may be able to see information about APIs they do not have permission for.\n\n* A malicious account-holder may be able to sign up to APIs they do not have permission for, and hence access API Management-protected resources they are not authorized to access.\n\n* This does NOT relate to the Apiman Gateway.\n\n### Patches\n\n* Upgrade to Apiman 3.0.0.Final (or later). The issue is fixed in this version.\n\n* If you are using an older version of Apiman, contact to your [Apiman support provider](https://www.apiman.io/support.html) for advice/long-term support.\n\n### References\n\n* https://www.apiman.io/blog/permissions-bypass-disclosure/\n* https://github.com/advisories/GHSA-54r5-wr8x-x5v3\n* https://nvd.nist.gov/vuln/detail/CVE-2022-47551\n* https://github.com/orgs/apiman/discussions/2409\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.apiman:apiman-manager-api-rest-impl"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.5.7"
}, {
"fixed" : "3.0.0.Final"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.2.3.Final"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/apiman/apiman/security/advisories/GHSA-j94p-hv25-rm5g"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-47551"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-54r5-wr8x-x5v3"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apiman/apiman"
}, {
"type" : "WEB",
"url" : "https://github.com/orgs/apiman/discussions/2409"
}, {
"type" : "WEB",
"url" : "https://www.apiman.io/blog/permissions-bypass-disclosure"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2023-01-03T12:28:06Z",
"nvd_published_at" : null
}
}