GHSA-54r5-wr8x-x5v3: Duplicate Advisory Apiman Has Insufficient Checks For Vulnerability
HIGHGHSA-54r5-wr8x-x5v3 is a HIGH (CVSS 7.1) apiman has insufficient checks for vulnerability (CWE-280: Improper Handling of Insufficient Permissions or Privileges) affecting Duplicate Advisory libraries in the Maven ecosystem. The issue involves apiman has insufficient checks for read permissions. Remediation is available by upgrading affected packages to version 3.0.0.Final.
GHSA-54r5-wr8x-x5v3 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 GHSA-54r5-wr8x-x5v3
To remediate this vulnerability, upgrade all affected Duplicate Advisory 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.apiman
How to Check if You Are Affected
To determine whether your Java application is affected by GHSA-54r5-wr8x-x5v3, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.apiman
Analyze the terminal output to locate any version of Duplicate Advisory 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 CWE-280: Improper Handling of Insufficient Permissions or Privileges, where the product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. this may cause it to follow unexpected code paths that may leave the product in an invalid state. In Duplicate Advisory, 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
GHSA-54r5-wr8x-x5v3 Affected Duplicate Advisory 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 GHSA-54r5-wr8x-x5v3?
Which Duplicate Advisory versions are affected?
What version fixes GHSA-54r5-wr8x-x5v3?
Is apiman-manager-api-rest-impl affected?
What is the CVSS score of GHSA-54r5-wr8x-x5v3?
What CWE is associated with GHSA-54r5-wr8x-x5v3?
How can I check Maven dependencies for GHSA-54r5-wr8x-x5v3?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-54r5-wr8x-x5v3",
"modified" : "2024-10-07T21:00:34Z",
"published" : "2022-12-20T00:30:27Z",
"withdrawn" : "2024-10-07T21:00:34Z",
"aliases" : [ ],
"summary" : "Duplicate Advisory: Apiman has insufficient checks for read permissions",
"details" : "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-j94p-hv25-rm5g. This link is maintained to preserve external references.\n\n## Original Description\nApiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. A malicious user may be able to find and subscribe to private APIs they do not have permission for, thus accessing API Management-protected resources they should not be allowed to access. 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.",
"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" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-47551"
}, {
"type" : "WEB",
"url" : "https://github.com/apiman/apiman/discussions/2409"
}, {
"type" : "WEB",
"url" : "https://www.apiman.io/blog/permissions-bypass-disclosure"
}, {
"type" : "PACKAGE",
"url" : "https://www.github.com/apiman/apiman"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-276", "CWE-280" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-12-20T17:37:18Z",
"nvd_published_at" : "2022-12-20T00:15:00Z"
}
}