How to fix: Jenkins version disclosed in response
The HTTP response reveals the Jenkins CI server version, either via headers or page content.
Why it matters
Knowing the exact Jenkins version allows attackers to search for applicable CVEs and exploit unpatched vulnerabilities. Jenkins has had numerous critical RCE vulnerabilities tied to specific versions.
Jenkins includes its version in the X-Jenkins header and sometimes in the HTML response. Both should be suppressed or Jenkins should not be publicly accessible.
How to fix it
- 1Jenkins should not be publicly accessible: place it behind a VPN or IP allowlist
- 2If public access is required, use a reverse proxy that strips the X-Jenkins header
- 3Keep Jenkins updated to the latest LTS release
Code examples
Nginx: strip Jenkins headers
proxy_hide_header X-Jenkins;
proxy_hide_header X-Jenkins-Session;
proxy_hide_header X-Hudson;References
Detected automatically by VulnRadar. The check id is jenkins-version-exposure, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is Jenkins version disclosed in response?
- VulnRadar rates this low severity in the info disclosure 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 jenkins-version-exposure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Jenkins version disclosed 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.