Apiman prior 3.1.0.Final API Key privileges management

Summaryinfo

A vulnerability categorized as critical has been discovered in Apiman. Affected by this issue is some unknown functionality of the component API Key Handler. The manipulation results in privileges management. This vulnerability was named CVE-2023-28640. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Apiman. Affected is an unknown functionality of the component API Key Handler. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was presented 03/28/2023 as GHSA-m6f8-hjrv-mw5f. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2023-28640 since 03/20/2023. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.

Upgrading to version 3.1.0.Final eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Apiman

Website

• Product: https://github.com/apiman/apiman/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion