How to fix: Server version disclosed in response header
A response header carries a value that matches a version-like pattern (e.g. '1.0', '2.3.1').
Why it matters
Version strings in headers give attackers a target list of CVEs without further probing.
Headers like Server, X-Powered-By, X-AspNet-Version, NEL, and Report-To frequently leak exact upstream versions. Strip them at the edge or use generic placeholders.
How to fix it
- 1Set server_tokens off; in nginx or strip the Server header at the reverse proxy.
- 2Disable X-Powered-By by setting `poweredByHeader: false` in Next.js or removing the Express x-powered-by setting.
- 3Genericize NEL and Report-To headers or remove the 'version' field.
Code examples
Nginx
server_tokens off;
proxy_hide_header X-Powered-By;
proxy_hide_header Server;Next.js
const nextConfig = { poweredByHeader: false };References
Detected automatically by VulnRadar. The check id is version-disclosure, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- MediumSensitive Keywords in HTML Comments
Questions
- How severe is Server version disclosed in response header?
- VulnRadar rates this low severity in the content 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 version-disclosure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Server version disclosed in response header 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.