How to fix: X-AspNet-Version header exposes ASP.NET version
The X-AspNet-Version header is present and reveals the exact ASP.NET framework version.
Why it matters
The specific ASP.NET version allows attackers to immediately identify applicable CVEs and security patches that have not been applied, narrowing exploit selection.
Disable the X-AspNet-Version header in your application configuration.
How to fix it
- 1In Web.config: <httpRuntime enableVersionHeader="false" />
- 2Or via custom header removal in Global.asax
Code examples
Web.config
<configuration>
<system.web>
<httpRuntime enableVersionHeader="false" />
</system.web>
</configuration>References
Detected automatically by VulnRadar. The check id is x-aspnet-version-exposed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-AspNet-Version header exposes ASP.NET version?
- 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 x-aspnet-version-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-AspNet-Version header exposes ASP.NET version 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.