GrafanaApplication
CVE-2021-28148
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 · uneditedOne of the usage insights HTTP API endpoints in Grafana Enterprise 6.x before 6.7.6, 7.x before 7.3.10, and 7.4.x before 7.4.5 is accessible without any authentication. This allows any unauthenticated user to send an unlimited number of requests to the endpoint, leading to a denial of service (DoS) attack against a Grafana Enterprise instance.
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 confidenceGrafana Enterprise versions 6.x before 6.7.6, 7.x before 7.3.10, and 7.4.x before 7.4.5 have an unauthenticated usage insights HTTP API endpoint that accepts requests without any authentication, enabling attackers to flood the endpoint and cause denial of service.
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
>= 6.0.0, < 6.7.6>= 7.0.0, < 7.3.10>= 7.4.0, < 7.4.5CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Grafana installationRun 'grafana-server -v' or 'grafana-cli --version' to get the version, or check the installed package (dpkg -l grafana or rpm -qi grafana)Affected if Grafana is not installed or cannot be determined
-
Check installed Grafana versionUse the Grafana HTTP API: curl -s http://localhost:3000/api/health or inspect the binary: ./grafana-server -vAffected if Version cannot be retrieved
-
Compare version against affected rangesReview the version output and compare against: 6.0.0 to 6.7.6 (exclusive), 7.0.0 to 7.3.10 (exclusive), 7.4.0 to 7.4.5 (exclusive)Affected if Version falls within any of these ranges: >= 6.0.0 and < 6.7.6, OR >= 7.0.0 and < 7.3.10, OR >= 7.4.0 and < 7.4.5
-
Verify usage insights feature statusCheck Grafana configuration file (grafana.ini) for 'enable_usage_insights' setting under [analytics] section, or inspect UI: Settings > AnalyticsAffected if Usage insights is enabled on an affected version
If Grafana Enterprise is installed with a version in the affected ranges (6.x < 6.7.6, 7.x < 7.3.10, or 7.4.x < 7.4.5) and usage insights feature is enabled, the environment is vulnerable to unauthenticated DoS attacks via the usage insights endpoint.
Generated from the published advisory. Verify against your own configuration.
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 data6.7.67.3.107.4.5
Upgrade Grafana Enterprise to version 6.7.6, 7.3.10, 7.4.5 or later to apply the authentication fix and prevent unauthenticated access to the usage insights endpoint.
Fix this in Grafana
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-28148 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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