How to fix: Grafana version disclosed in response
The Grafana dashboard version is exposed in HTTP headers or page content.
Why it matters
A published version number turns a general question into a lookup: an attacker reads the advisories for that exact release rather than probing. Whether that matters here depends on the version, and the evidence line says which case this is. Grafana 8.0.0 through 8.3.0 is the range affected by CVE-2021-43798, an unauthenticated path traversal on CISA's Known Exploited Vulnerabilities list; a version outside that range is a fingerprint rather than a live exposure.
Grafana publishes its version in the X-Grafana-Version header and in the login page HTML. This check reads that version and compares it against the range affected by CVE-2021-43798 rather than citing the CVE at every install it finds. The finding stays low severity either way, because the disclosure itself is what is being reported; if the version is in the affected range the evidence says so, and that is the part to act on first.
How to fix it
- 1Read the evidence line: if it names CVE-2021-43798, upgrade Grafana before anything else
- 2Place Grafana behind a VPN or require authentication at the network level
- 3Use a reverse proxy to strip version-identifying headers
- 4Keep Grafana updated to the latest stable version
Code examples
Nginx reverse proxy for Grafana
location /grafana/ {
proxy_pass http://localhost:3000/;
proxy_hide_header X-Grafana-Org-ID;
proxy_set_header Host $http_host;
# Add authentication:
auth_basic "Restricted";
auth_basic_user_file /etc/nginx/.htpasswd;
}References
Detected automatically by VulnRadar. The check id is grafana-version-exposure, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is Grafana version disclosed in response?
- VulnRadar rates this low severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id grafana-version-exposure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Grafana version disclosed in response map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.