CVE-2019-10405: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
Summary
CVE-2019-10405: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.176.4
>= 2.177, < 2.197
Fixed in 2.176.4 or 2.197, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Jenkins is an open-source automation server that enables developers to build, test, and deploy their software projects. It is widely used in the software development industry due to its flexibility and extensive plugin ecosystem. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its basic functionality.
Vulnerability Detail
The vulnerability identified as CVE-2019-10405 in Jenkins versions 2.196 and earlier, LTS 2.176.3 and earlier, allows an unauthorized actor to access sensitive information. Specifically, the value of the 'Cookie' HTTP request header is printed on the '/whoAmI/' URL. This exposes the HTTP session cookie, which is marked as HttpOnly, to potential attackers. Exploiting another XSS vulnerability, an attacker can obtain this session cookie and potentially hijack the user's session.
How To Fix
Latest published version: 2.587 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.176.42.176.4 -
>= 2.177, < 2.1972.197
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, users can manually remove the 'Cookie' header from the HTTP request before accessing the '/whoAmI/' URL. This can be achieved by modifying the relevant code or using a reverse proxy to filter out the 'Cookie' header. However, this workaround is not a permanent solution and should be replaced with the recommended fix as soon as possible.
Conclusion
The vulnerability in Jenkins allows an unauthorized actor to access sensitive information by exposing the HTTP session cookie. It is crucial to apply the recommended fix by upgrading to the specified versions of Jenkins. In the meantime, a temporary workaround can be implemented to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
Jenkins is an open-source automation server used for continuous integration and continuous delivery (CI/CD) of software projects.
The vulnerable package is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its basic functionality.
This vulnerability allows an unauthorized actor to obtain the HTTP session cookie, potentially leading to session hijacking and unauthorized access to the user's account.
To fix this vulnerability, it is recommended to upgrade to Jenkins version 2.176.4 or later for LTS releases, and version 2.197 or later for non-LTS releases.
Yes, a temporary workaround is to manually remove the 'Cookie' header from the HTTP request before accessing the '/whoAmI/' URL.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
