InfluxDB 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. The supplier has stated that InfluxDB 2.8.0 has addressed this issue.
InfluxDB OSS 2.x stores the operator token (with highest privileges) in the authorization resource of the default organization. Any user with read permissions to the authorization resource in the default organization can retrieve this token. Additionally, users with the allAccess administrator role can retrieve all tokens in plain text using the 'influx auth ls' command. The vendor indicates that the organization mechanism works as intended, however it did not adequately protect the operator token from being read by regular administrators.
An attacker with read access to authorization resources in the default organization can obtain the operator token and gain full administrative control over the InfluxDB instance, leading to disclosure, modification, or deletion of all stored data.
InfluxDB OSS should be updated to version 2.8.0, in which the vendor removed the ability to retrieve tokens via API. Additionally, it is recommended to migrate users from the default organization to custom organizations and perform operator token rotation to invalidate potentially compromised credentials.
InfluxDB OSS versions 2.x through 2.7.11. Versions 1.x, Enterprise, Cloud, Cloud Dedicated, and Clustered are not affected.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H