CVE-2024-1442: User with permissions to create a data source can CRUD all data sources
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.80% (FIRST EPSS); higher than 57.1% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Grafana Grafana 10.0.12, 10.1.8, 10.2.5.
- Severity is disputed: the assigning authority (CNA) scores it 6.0, NVD 8.8.
Low priority for now. Upgrade to Grafana Grafana 10.0.12, 10.1.8, 10.2.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A user with the permissions to create a data source can use Grafana API to create a data source with UID set to *. Doing this will grant the user access to read, query, edit and delete all data sources within the organization.
- Published
- Mar 7, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-269
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · GRAFANA
- 6.0
- 2.8 point gap
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| grafana | grafana | cpe:2.3:a:grafana:grafana |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GRAFANA). Independent of NVD's CPE analysis and usually ahead of it.
Grafana Grafana
- 8.5.0 and later · before 9.5.7affected · semver
- 10.0.0 and later · before 10.0.12affected · semver
- 10.1.0 and later · before 10.1.8affected · semver
- 10.2.0 and later · before 10.2.5affected · semver
- 10.3.0 and later · before 10.3.4affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- grafana grafana8.5.0 and later · before 9.5.7
- grafana grafana10.0.0 and later · before 10.0.12
- grafana grafana10.1.0 and later · before 10.1.8
- grafana grafana10.2.0 and later · before 10.2.5
- grafana grafana10.3.0 and later · before 10.3.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/grafana/grafana | from 0 | — |
| Go | github.com/grafana/grafana | from 10.0.0 · before 10.0.12 | 10.0.12 |
| Go | github.com/grafana/grafana | from 10.1.0 · before 10.1.8 | 10.1.8 |
| Go | github.com/grafana/grafana | from 10.2.0 · before 10.2.5 | 10.2.5 |
| Go | github.com/grafana/grafana | from 10.3.0 · before 10.3.4 | 10.3.4 |
| Go | github.com/grafana/grafana | from 8.5.0 · before 9.5.7 | 9.5.7 |
Same product
grafana: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-39226Snapshot authentication bypass in grafanaKEV89Now
- CVE-2021-43798Grafana path traversalKEV87Now
- CVE-2024-9264Grafana SQL Expressions allow for remote code execution66This week
Published before and after this one in the same product
- ← EarlierCVE-2023-6152Feb 13, 2024 · A user changing their email after signing up and verifying it can change it without verification in profile settings.21Monitor
- ← EarlierCVE-2023-5122Feb 14, 2024 · SSRF in CSV Datasource Plugin21Monitor
- Later →CVE-2024-1313Mar 26, 2024 · Users outside an organization can delete a snapshot with its key26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Grafana Grafana | 10.0.12 | Vendor (CNA) |
| Grafana Grafana | 10.1.8 | Vendor (CNA) |
| Grafana Grafana | 10.2.5 | Vendor (CNA) |
| Grafana Grafana | 10.3.4 | Vendor (CNA) |
| Grafana Grafana | 9.5.7 | Vendor (CNA) |
| Go:github.com/grafana/grafana | 10.0.12 | Package registry (OSV) |
| Go:github.com/grafana/grafana | 10.1.8 | Package registry (OSV) |
| Go:github.com/grafana/grafana | 10.2.5 | Package registry (OSV) |
| Go:github.com/grafana/grafana | 10.3.4 | Package registry (OSV) |
| Go:github.com/grafana/grafana | 9.5.7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-4822143 days apartGrafana is an open-source platform for monitoring and observability.28Monitor
Bug bounty scope
- Grafana Labs - Vulnerability Disclosure Program (VDP)Intigriti · disclosure only (VDP) · grafana/grafana
- Grafana Labs - Vulnerability Disclosure Program (VDP)Intigriti · disclosure only (VDP)
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.