CVE-2024-30896 affects InfluxDB OSS 2.x through 2.7.11, allowing authorized users with read access to the authorization resource of the default organization to retrieve the administrative operator token. This vulnerability carries a critical CVSS score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), indicating a high-impact network-exploitable flaw that can lead to complete compromise. While not currently on the KEV catalog, an ExploitDB entry (EDB-52142) exists, and the vulnerability has garnered significant community discussion, suggesting potential for future exploitation. InfluxDB 2.8.0 reportedly addresses this issue.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
| N/A | N/A | n/aCNA affected |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.7 Bluesky, 0.4 Mastodon, and 1.7 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.4 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
InfluxDB: Privilege Escalation via Authorization Token in InfluxDB
Nov 21, 2024InfluxDB OSS 2.x through 2.7.11 stores the administrative operator token under the default organization which allows authorized users with read access to the authorization resource of the default organization to retrieve the operator token. InfluxDB OSS 1.x, Enterprise, Cloud, Cloud Dedicated and Clustered are not affected. NOTE: The researcher states that InfluxDB allows allAccess administrators to retrieve all raw tokens via an "influx auth ls" command. The supplier indicates that the organizations feature is operating as intended and that users may choose to add users to non-default organizations. A future release of InfluxDB 2.x will remove the ability to retrieve tokens from the API.
Nov 12, 2024