How to fix: Internal API version exposed in response
The API response includes an internal version string or build number that reveals implementation details.
Why it matters
Exposed API version strings allow attackers to look up known CVEs for that specific version and target unpatched vulnerabilities. Version enumeration is often the first step in a targeted attack.
API responses should not include internal version numbers or build identifiers.
How to fix it
- 1Remove version strings from API response bodies
- 2Remove X-Powered-By, X-Version, X-Build-Number headers
- 3Use semantic versioning in URL paths (/api/v2/) without exposing internal build numbers
Code examples
Remove API version from response headers
// Remove version information from response headers
app.use((req, res, next) => {
res.removeHeader('X-Powered-By');
res.removeHeader('Server');
// Don't expose: res.setHeader('X-API-Version', '2.1.0');
next();
});References
Detected automatically by VulnRadar. The check id is exposed-api-version, 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
- LowServer version disclosed in response header
Questions
- How severe is Internal API version exposed in response?
- 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 exposed-api-version, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Internal API version exposed 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.