CVE-2023-28640: Apiman manager api rest impl Apiman Vulnerable To Permissions Bypass Vulnerability
MODERATECVE-2023-28640 is a MODERATE (CVSS 6.4) apiman vulnerable to permissions bypass vulnerability (CWE-269: Improper Privilege Management) affecting Apiman manager api rest impl libraries in the Maven ecosystem. The issue involves apiman vulnerable to permissions bypass due to missing check on api key url. Remediation is available by upgrading affected packages to version 3.1.0.Final.
CVE-2023-28640 at a Glance
Security Impact
CVSS: 6.4
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:C/C:L/I:L/A:N).
How to Fix CVE-2023-28640
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.1.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-2023-28640, 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.1.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-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. 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-2023-28640 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 |
< 3.1.0.Final
|
3.1.0.Final
|
References
Frequently Asked Questions
What is CVE-2023-28640?
Which Apiman manager api rest impl versions are affected?
What version fixes CVE-2023-28640?
Is apiman-manager-api-rest-impl affected?
What is the CVSS score of CVE-2023-28640?
What CWE is associated with CVE-2023-28640?
How can I check Maven dependencies for CVE-2023-28640?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m6f8-hjrv-mw5f",
"modified" : "2023-03-27T22:17:57Z",
"published" : "2023-03-27T22:17:57Z",
"aliases" : [ "CVE-2023-28640" ],
"summary" : "Apiman vulnerable to permissions bypass due to missing check on API key URL",
"details" : "### Impact\n\nDue to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL. The URL includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource, and each of these can have arbitrary values.\n\nWhile not trivial to exploit, it could be achieved by brute-forcing or guessing common names.\n\nAccess to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security).\n\n### Patches\n\nApiman 3.1.0.Final and later resolves this issue. \n\n### Workarounds\n\nOnly provide Apiman Manager accounts to known users, do not allow anonymous/unknown users to create an Apiman Manager account.\n\nNote that this does **not** affect the Apiman Gateway.\n\n### References\n\n* [Blog post disclosing issue](https://www.apiman.io/blog/potential-permissions-bypass-disclosure/)\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.apiman:apiman-manager-api-rest-impl"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.1.0.Final"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "< 3.0.0.Final"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/apiman/apiman/security/advisories/GHSA-m6f8-hjrv-mw5f"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-28640"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apiman/apiman"
}, {
"type" : "WEB",
"url" : "https://www.apiman.io/blog/potential-permissions-bypass-disclosure"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-269", "CWE-280", "CWE-862" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2023-03-27T22:17:57Z",
"nvd_published_at" : "2023-03-27T21:15:00Z"
}
}