dbcve.org
GrafanaApplication

CVE-2023-4399

HIGH · 7.2 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 9.4.17 / 9.5.13 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Grafana is an open-source platform for monitoring and observability. In Grafana Enterprise, Request security is a deny list that allows admins to configure Grafana in a way so that the instance doesn’t call specific hosts. However, the restriction can be bypassed used punycode encoding of the characters in the request address.

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

In Grafana Enterprise, the Request Security feature uses a deny list to block Grafana from calling specific hosts. This protection can be bypassed by using punycode encoding (Unicode characters that visually resemble ASCII letters) in the request address, allowing attackers to make Grafana call hosts that should be blocked by the deny list.

MitigationUpdate to the patched Grafana Enterprise version. Consider implementing allow-listing instead of deny-listing for request security as a defense-in-depth measure.

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:>= 9.4.0, < 9.4.17>= 9.5.0, < 9.5.13>= 10.0.0, < 10.0.9>= 10.1.0, < 10.1.5

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Check Grafana Enterprise version
    Run 'grafana-server -v' or check the version via the Grafana HTTP API at /api/health, or inspect the installed package version
    Affected if The installed version falls within any of these ranges: 9.4.0-9.4.16, 9.5.0-9.5.12, 10.0.0-10.0.8, or 10.1.0-10.1.4
  2. Confirm Grafana Enterprise edition
    Check the Grafana UI footer or API response for 'Enterprise' label, or check the license file
    Affected if The edition is Grafana Enterprise (the vulnerability affects Enterprise only, not open source)
  3. Verify Request Security feature is enabled
    Inspect the Grafana configuration file (grafana.ini) for the 'request_security' section or check if the feature flag is active
    Affected if Request Security is configured with a deny list rule set (the bypass only matters if deny-listing is in use)
  4. Review deny list configuration
    Examine the Grafana configuration for blocked hosts or domains under the Request Security settings
    Affected if There are deny list entries present that block specific hosts or domains
  5. Test punycode bypass hypothesis
    If deny list is active, compare how the system handles a blocked domain versus its punycode equivalent (for example, 'example.com' vs 'xn--exmple-cua.com')
    Affected if The punycode variant of a blocked domain would be allowed while the ASCII version is denied, indicating the bypass works

You are affected if you run Grafana Enterprise within the vulnerable version ranges AND have Request Security deny-listing enabled with rules that could be bypassed via punycode-encoded hostnames.

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.

dbcve · scoped
Upgrade available Upgrade to 9.4.17 / 9.5.13 / 10.0.9 or later
Fixed in 9.4.179.5.1310.0.9
Interim mitigation

Update to the patched Grafana Enterprise version. Consider implementing allow-listing instead of deny-listing for request security as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to Grafana 9.4.17, 9.5.13, 10.0.9, or 10.1.5 (or latest 10.x patch) based on your current major version branch

  1. 1. Backup your Grafana configuration, dashboards, and database
  2. 2. Stop the Grafana service
  3. 3. Download the appropriate fixed version for your current major version (9.4.17+, 9.5.13+, 10.0.9+, or 10.1.5+)
  4. 4. Replace the Grafana binaries with the fixed version
  5. 5. Verify configuration files are compatible with the new version
  6. 6. Start the Grafana service
  7. 7. Test that Request Security deny list configurations properly block punycode-encoded hosts
  8. 8. Monitor logs for any errors
Caveat Minor version upgrades typically retain compatibility; review release notes for deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4399 — 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-2023-4399 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