How to fix: Via header reveals proxy infrastructure
The Via header is present and reveals proxy server software names or versions in the request chain.
Why it matters
The Via header can reveal internal proxy names, software versions, or infrastructure topology, giving attackers a map of the request chain and potential pivot points.
Strip or genericize the Via header at your edge proxy.
How to fix it
- 1Configure your CDN/proxy to remove or genericize the Via header
- 2Nginx: proxy_set_header Via "";
- 3Ensure internal hostnames are not reflected in Via headers
Code examples
Nginx: remove Via
proxy_hide_header Via;
# Or replace with a generic value:
proxy_set_header Via "";References
Detected automatically by VulnRadar. The check id is via-header-exposed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Via header reveals proxy infrastructure?
- 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 via-header-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Via header reveals proxy infrastructure 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.