How to fix: Server header discloses software identity
The HTTP Server response header identifies the web server software by name.
Why it matters
Knowing the server software (nginx, Apache, IIS, etc.) enables targeted vulnerability scanning against known CVEs for that software and version, reducing the effort needed for an attack.
Remove or genericize the Server header to reduce information leakage.
How to fix it
- 1Nginx: add "server_tokens off;" in the http block
- 2Apache: set "ServerTokens Prod" and "ServerSignature Off"
- 3Next.js: set poweredByHeader: false in next.config.mjs
Code examples
Nginx
# In nginx.conf http block:
server_tokens off;
# This removes the version; to hide the server name entirely:
# server_tokens "VulnRadar"; # or any generic stringApache
ServerTokens Prod
ServerSignature OffReferences
Detected automatically by VulnRadar. The check id is server-header-disclosure, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Server header discloses software identity?
- VulnRadar rates this low severity in the headers 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 server-header-disclosure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Server header discloses software identity 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.