Snapshot authentication bypass in grafana
Affects Grafana releases before 7.5.11 and 8.0.0 through 8.1.5. Fixed in 7.5.11 and 8.1.6.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 8.1.6, 7.5.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Grafana, an open source data visualization platform, is affected by this vulnerability in its snapshot feature. Unauthenticated and authenticated users can view, and in some cases delete, snapshot data they should not have access to, which can lead to complete loss of snapshot data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Grafana is an open source data visualization platform. In affected versions unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths: /dashboard/snapshot/:key, or /api/snapshots/:key. If the snapshot "public_mode" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path: /api/snapshots-delete/:deleteKey. Regardless of the snapshot "public_mode" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths: /api/snapshots/:key, or /api/snapshots-delete/:deleteKey. The combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss. This issue has been resolved in versions 8.1.6 and 7.5.11. If for some reason you cannot upgrade you can use a reverse proxy or similar to block access to the literal paths: /api/snapshots/:key, /api/snapshots-delete/:deleteKey, /dashboard/snapshot/:key, and /api/snapshots/:key. They have no normal function and can be disabled without side effects.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- grafana grafana
From 8.0.0 · fixed in 8.1.6; fixed in 7.5.11
- github.com/grafana/grafanaGo
fixed in 7.5.11
- github.com/grafana/grafanaGo
From 8.0.0 · fixed in 8.1.6
References 8
GitHub · grafana/grafana
grafana.com
openwall.com
lists.fedoraproject.org
security.netapp.com
Questions about CVE-2021-39226
What should I do about it?
Upgrade to Grafana 7.5.11 if you run a release before 8.0.0, or to 8.1.6 if you run 8.0.0 through 8.1.5. The advisory's fix note names upstream 7.5.11.Source: lists.fedoraproject.org
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-08-25, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data