dbcve.org
GrafanaApplication

CVE-2019-15043

HIGH · 7.5 CVSS v3.0 Published 2019-09-03
Fix available
A fix is available. Upgrade to 5.4.5 / 6.3.4 or later.
See remediation →
84/100
Remediation priority · High
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Grafana 2.x through 6.x before 6.3.4, parts of the HTTP API allow unauthenticated use. This makes it possible to run a denial of service attack against the server running Grafana.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Grafana versions 2.x through 6.x before 6.3.4 have an authentication bypass vulnerability in parts of the HTTP API. Unauthenticated attackers can access certain API endpoints, enabling them to launch denial of service attacks by exhausting server resources or causing crashes.

MitigationUpgrade Grafana to version 6.3.4 or later. If immediate patching is not possible, implement network-level access controls to restrict untrusted access to the Grafana HTTP API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 2.0.0, < 5.4.5>= 6.0.0, < 6.3.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana version from the UI
    Log into the Grafana web interface and navigate to the Help icon (question mark) in the left sidebar, then select 'Version' to display the installed Grafana version
    Affected if The displayed version falls within 2.0.0 to 5.4.4 or 6.0.0 to 6.3.3
  2. Identify Grafana version from the command line
    Run the command 'grafana-server -v' or 'grafana-cli --version' if the binary is accessible on the host, or check the package manager output such as 'dpkg -l grafana' or 'rpm -qi grafana'
    Affected if The returned version falls within 2.0.0 to 5.4.4 or 6.0.0 to 6.3.3
  3. Identify Grafana version from configuration files
    Check the Grafana installation directory for a 'version' file, or inspect the '/usr/share/grafana/version' file on Linux systems installed via package managers
    Affected if The version file contains a version number within 2.0.0 to 5.4.4 or 6.0.0 to 6.3.3

You are affected if your Grafana instance version is 2.0.0 through 5.4.4 or 6.0.0 through 6.3.3, as these versions contain the authentication bypass in the HTTP API that allows unauthenticated access to certain endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 5.4.5 / 6.3.4 or later
Fixed in 5.4.56.3.4
Interim mitigation

Upgrade Grafana to version 6.3.4 or later. If immediate patching is not possible, implement network-level access controls to restrict untrusted access to the Grafana HTTP API endpoints.

Fix this in Grafana Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15043 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data