First published: Wed Sep 25 2019(Updated: )
Jenkins 2.196 and earlier, LTS 2.176.3 and earlier printed the value of the "Cookie" HTTP request header on the /whoAmI/ URL, allowing attackers exploiting another XSS vulnerability to obtain the HTTP session cookie despite it being marked HttpOnly.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.main:jenkins-core | >=2.177<=2.196 | 2.197 |
maven/org.jenkins-ci.main:jenkins-core | <=2.176.3 | 2.176.4 |
Jenkins LTS | <=2.176.3 | |
Jenkins LTS | <=2.196 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10405 is considered a medium severity vulnerability due to its potential for session hijacking through exposed HTTP session cookies.
To fix CVE-2019-10405, upgrade Jenkins to version 2.197 or later, or to version 2.176.4 or later for LTS.
CVE-2019-10405 affects Jenkins versions up to 2.196 and LTS versions up to 2.176.3.
The impact of CVE-2019-10405 allows attackers to exploit a cross-site scripting vulnerability to retrieve HTTP session cookies from affected Jenkins instances.
CVE-2019-10405 is considered moderately exploitable as it requires an attacker to leverage another XSS vulnerability.