CVE-2019-19499: Grafana <= 6.4.3 has an Arbitrary File Read vulnerability, which could be exploited by an authenticated attacker that has privileges to modi
Noroxi assessment
Priority: Monitor (action score 27/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: 3.5% (FIRST EPSS); higher than 89.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 (AlmaLinux:8) 6.7.4-3.el8; grafana-azure-monitor (AlmaLinux:8) 6.7.4-3.el8; grafana-cloudwatch (AlmaLinux:8) 6.7.4-3.el8.
Low priority for now. Upgrade to grafana (AlmaLinux:8) 6.7.4-3.el8; grafana-azure-monitor (AlmaLinux:8) 6.7.4-3.el8; grafana-cloudwatch (AlmaLinux:8) 6.7.4-3.el8 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
Grafana <= 6.4.3 has an Arbitrary File Read vulnerability, which could be exploited by an authenticated attacker that has privileges to modify the data source configurations.
- Published
- Aug 28, 2020
- Updated
- Jun 16, 2026
- EPSS
- 3.5% · 89th percentile
- CWE
- CWE-89
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.5%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- grafana grafanaup to 6.4.3 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | grafana | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-azure-monitor | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-cloudwatch | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-elasticsearch | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-graphite | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-influxdb | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-loki | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-mssql | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-mysql | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-opentsdb | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-postgres | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-prometheus | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| AlmaLinux:8 | grafana-stackdriver | before 6.7.4-3.el8 | 6.7.4-3.el8 |
| Go | github.com/grafana/grafana | from 0 | — |
| Go | github.com/grafana/grafana | before 6.4.4 | 6.4.4 |
| Red Hat:enterprise_linux:8::appstream | grafana | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-azure-monitor | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-cloudwatch | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-debuginfo | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-elasticsearch | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-graphite | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-influxdb | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-loki | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
| Red Hat:enterprise_linux:8::appstream | grafana-mssql | before 0:6.7.4-3.el8 | 0:6.7.4-3.el8 |
+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-2020-13379Jun 3, 2020 · The avatar feature in Grafana 3.0.1 through 7.0.1 has an SSRF Incorrect Access Control issue.62This week
- ← EarlierCVE-2020-11110Jul 27, 2020 · Grafana through 6.7.1 allows stored XSS due to insufficient input protection in the originalUrl field, which allows an attacker to inject Ja24Monitor
- Later →CVE-2020-24303Oct 28, 2020 · Grafana before 7.1.0-beta 1 allows XSS via a query alias for the ElasticSearch datasource.25Monitor
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 |
|---|---|---|
| almalinux:grafana | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-azure-monitor | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-cloudwatch | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-elasticsearch | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-graphite | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-influxdb | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-loki | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-mssql | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-mysql | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-opentsdb | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-postgres | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-prometheus | 6.7.4-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| Go:github.com/grafana/grafana | 6.4.4 | Package registry (OSV) |
| red hat:grafana | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-azure-monitor | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-cloudwatch | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-debuginfo | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-elasticsearch | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-graphite | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-influxdb | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-loki | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-mssql | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-mysql | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-opentsdb | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-postgres | 0:6.7.4-3.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| suse:grafana | 7.3.1-3.6.1 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
| suse:system-user-grafana | 1.0.0-3.9.1 · SUSE:Manager Client Tools 15 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
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.
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
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.