CVE-2023-6152GHSA-3HV4-R2FM-H27FBIT-GRAFANA-2023-6152
A user changing their email after signing up and verifying it can change it without verification in profile settings.
- 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? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.5.16, 10.0.11, 10.1.7, 10.2.4, 10.3.3
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
A user changing their email after signing up and verifying it can change it without verification in profile settings. The configuration option "verify_email_enabled" will only validate email only on sign up.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Grafana Grafana
From 2.5.0 · fixed in 9.5.16; From 10.0.0 · fixed in 10.0.11; From 10.1.0 · fixed in 10.1.7; From 10.2.0 · fixed in 10.2.4; From 10.3.0 · fixed in 10.3.3
- Grafana Grafana Enterprise
From 2.5.0 · fixed in 9.5.16; From 10.0.0 · fixed in 10.0.11; From 10.1.0 · fixed in 10.1.7; From 10.2.0 · fixed in 10.2.4; From 10.3.0 · fixed in 10.3.3
- github.com/grafana/grafanaGo
From 2.5.0 · fixed in 9.5.16
- github.com/grafana/grafanaGo
From 10.0.0 · fixed in 10.0.11
- github.com/grafana/grafanaGo
From 10.1.0 · fixed in 10.1.7
- github.com/grafana/grafanaGo
From 10.2.0 · fixed in 10.2.4
- github.com/grafana/grafanaGo
From 10.3.0 · fixed in 10.3.3