Jenkins Diagnostic page exposed session cookies
Jenkins shows various technical details about the current user on the `/whoAmI` page. In [a previous fix](https://www.jenkins.io/security/advisory/2019-09-25/#SECURITY-1505), the `Cookie` header value containing the HTTP session ID was redacted. However, user metadata shown on this page could also include the HTTP session ID in Jenkins 2.218 and earlier, LTS 2.204.1 and earlier. This allows attackers able to exploit a cross-site scripting vulnerability to obtain the HTTP session ID value from this page. Jenkins 2.219, LTS 2.204.2 no longer prints out the affected user metadata that might contain the HTTP session ID. Additionally, we also redact values of further authentication-related HTTP headers in addition to `Cookie` on this page as a hardening.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-2103US | medium5.4 | — | ||
Jenkins 2.218 and earlier, LTS 2.204.1 and earlier exposed session identifiers on a user's detail object in the whoAmI diagnostic page. | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2020/01/29/1WEB
- https://access.redhat.com/errata/RHBA-2020:0402WEB
- https://access.redhat.com/errata/RHBA-2020:0675WEB
- https://access.redhat.com/errata/RHSA-2020:0681WEB
- https://access.redhat.com/errata/RHSA-2020:0683WEB
- https://github.com/jenkinsci/jenkinsPACKAGE
- https://github.com/jenkinsci/jenkins/commit/77f36f37f5e3cabd0e4ece16d46d7943454ed15bWEB
- https://jenkins.io/security/advisory/2020-01-29/#SECURITY-1695WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan