{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30896 exists.","fix":"No fix has been published for CVE-2024-30896 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-30896 is a critical vulnerability in n/a, published on 21 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-30896 and fix it if it is affected.\n\nWhat it is: CVE-2024-30896 is a critical vulnerability in n/a, published on 21 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30896 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-30896/ (Markdown: https://insights.sbomify.com/CVE-2024-30896/index.md)","id":"CVE-2024-30896","markdown":"https://insights.sbomify.com/CVE-2024-30896/index.md","name":"CVE-2024-30896","record":{"aliases":["AZL-53438","AZL-53622","GHSA-r5vq-m2mp-cpfj","UBUNTU-CVE-2024-30896"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"InfluxDB time-series database","requires_auth":"high_privilege","summary":"Authorized users with read access can retrieve the administrative operator token from the default organization, potentially leading to privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2024-03-22","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-03-22T16:50:40Z","kind":"github_poc","ref":"https://github.com/XenoM0rph97/CVE-2024-30896","stars":2,"title":null},{"date":"2025-04-08","kind":"exploitdb","ref":"52142","stars":null,"title":"InfluxDB OSS 2.7.11 - Operator Token Privilege Escalation"}],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2024-30896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-30915"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2024-30891"},"products":["n/a"],"published":"2024-11-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-19","vendors":["n/a"]},"summary":"Authorized users with read access can retrieve the administrative operator token from the default organization, potentially leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2024-30896/"}