{"answers":{"affected":"1 open source package ship an affected version, including grafana. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24812 in the wild and no public exploit code.","fix":"Upgrade grafana to 8.4.6 or later.","what":"CVE-2022-24812 is a high-severity vulnerability in Grafana Grafana, published on 12 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24812 and fix it if it is affected.\n\nWhat it is: CVE-2022-24812 is a high-severity vulnerability in Grafana Grafana, published on 12 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-24812 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- grafana (Bitnami): affected from 8.1.0; fixed in 8.4.6\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-2022-24812/ (Markdown: https://insights.sbomify.com/CVE-2022-24812/index.md)","id":"CVE-2022-24812","markdown":"https://insights.sbomify.com/CVE-2022-24812/index.md","name":"CVE-2022-24812","record":{"aliases":["BIT-grafana-2022-24812","GHSA-82gq-xfg3-5j7v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Grafana monitoring platform","requires_auth":"high_privilege","summary":"Attackers can escalate privileges by exploiting a caching flaw in Grafana Enterprise's fine-grained access control when multiple API keys are used.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"grafana","vendor":"grafana"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Grafana is an open-source platform for monitoring and observability. When fine-grained access control is enabled and a client uses Grafana API Key to make requests, the permissions for that API Key are cached for 30 seconds for the given organization. Because of the way the cache ID is constructed, the consequent requests with any API Key evaluate to the same permissions as the previous requests. This can lead to an escalation of privileges, when for example a first request is made with Admin permissions, and the second request with different API Key is made with Viewer permissions, the second request will get the cached permissions from the previous Admin, essentially accessing higher privilege than it should. The vulnerability is only impacting Grafana Enterprise when the fine-grained access control beta feature is enabled and there are more than one API Keys in one organization with different roles assigned. All installations after Grafana Enterprise v8.1.0-beta1 should be upgraded as soon as possible. As an alternative, disable fine-grained access control will mitigate the vulnerability.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"FGAC API Key privilege escalation in Grafana","id":"CVE-2022-24812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"grafana:grafana","products":["grafana:grafana"],"type":"privilege_escalation","year":"2022"},"n_packages":1,"n_references":4,"next":{"headline":"Authentication Bypass Using an Alternate Path or Channel in CreateWiki","id":"CVE-2022-24813"},"packages":[{"ecosystem":"Bitnami","fixed":["8.4.6"],"introduced":["8.1.0"],"last_affected":[],"package":"grafana","purl":"pkg:bitnami/grafana","source":"BIT-grafana-2022-24812"}],"prev":{"headline":"Cross-site Scripting in Combodo iTop","id":"CVE-2022-24811"},"products":["grafana"],"published":"2022-04-12","related":[{"cvss_score":7.5,"headline":"Grafana Path Traversal","id":"CVE-2021-43798","kev_date_added":"2025-10-09","published":"2021-12-07"},{"cvss_score":10,"headline":"Incorrect privilege assignment","id":"CVE-2025-41115","kev_date_added":null,"published":"2025-11-21"},{"cvss_score":9.8,"headline":"Grafana vulnerable to race condition allowing privilege escalation","id":"CVE-2022-39328","kev_date_added":null,"published":"2022-11-08"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-28660","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2022-26148","kev_date_added":null,"published":"2022-03-21"},{"cvss_score":9.8,"headline":"Grafana Authentication Bypass","id":"CVE-2018-15727","kev_date_added":null,"published":"2018-08-29"},{"cvss_score":9.4,"headline":"Grafana SQL Expressions allow for remote code execution","id":"CVE-2024-9264","kev_date_added":null,"published":"2024-10-18"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-28","vendors":["grafana"]},"summary":"Attackers can escalate privileges by exploiting a caching flaw in Grafana Enterprise's fine-grained access control when multiple API keys are used.","url":"https://insights.sbomify.com/CVE-2022-24812/"}