Approved changes feed: RSS · Atom
cpe:2.3:a:apiman:apiman:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Apiman (3e5c6220-e049-5e77-b479-d3a7bc24d8b1) |
|---|---|
| Product | Apiman (7bd46005-1bba-58a4-81b3-cf4446ad7bc3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/apiman/apiman |
purl2cpe | 2026-06-01 10:15:00.340504 |
pkg:maven/io.apiman/apiman |
purl2cpe | 2026-06-01 10:15:00.340507 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-28640 |
vulnerable | 2026-06-08 06:01:14.621259 |
Permissions bypass in Apiman could enable authenticated attacker to unpermitted API Key
MEDIUM (6.4)
Apiman is a flexible and open source API Management platform. Due 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, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access 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). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.
Published: 2023-03-27T20:46:33.400Z
Updated: 2025-02-19T15:13:47.538Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-47551 |
vulnerable | 2026-06-08 05:50:40.741071 |
Details available
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.
Published: 2022-12-19T00:00:00.000Z
Updated: 2025-04-17T14:24:12.467Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.