CVE-2017-1000398: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
Summary
CVE-2017-1000398: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.73.2
>= 2.74, < 2.84
Fixed in 2.73.2 or 2.84, 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Jenkins is an open-source automation server that enables developers to build, test, and deploy their software projects. It provides a wide range of features and plugins to support continuous integration and delivery. The Jenkins Core package is a fundamental component of Jenkins, responsible for its core functionality. Unfortunately, versions 2.73.1 and earlier, as well as 2.83 and earlier, of the Jenkins Core package are vulnerable to an exposure of sensitive information issue.
Vulnerability Detail
The vulnerability in Jenkins allows an unauthorized actor to access sensitive information through the remote API. Specifically, the API endpoint at /computer/(agent-name)/api exposes information about tasks, such as builds, currently running on the agent. This includes tasks that the current user does not have access to due to lack of Item/Read permission. The issue poses a risk of unauthorized access to sensitive data, potentially leading to information disclosure and unauthorized actions.
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.73.22.73.2 -
>= 2.74, < 2.842.84
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 workaround, users can restrict access to the affected API endpoint (/computer/(agent-name)/api) by configuring appropriate network or firewall rules. By blocking external access to this endpoint, the risk of unauthorized access to sensitive information can be reduced.
Conclusion
In conclusion, the vulnerability in Jenkins Core exposes sensitive information to unauthorized actors through the remote API. Upgrading to the fixed versions of Jenkins Core is the recommended solution. Restricting access to the affected API endpoint can serve as a temporary workaround. 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 delivery of software projects.
The Jenkins Core package is a fundamental component of Jenkins, responsible for its core functionality.
The vulnerability allows an unauthorized actor to access sensitive information, potentially leading to information disclosure and unauthorized actions.
To fix this vulnerability, upgrade to the recommended fixed versions of Jenkins Core (2.73.2 or later for the first range, and 2.84 or later for the second range).
Yes, you can restrict access to the affected API endpoint (/computer/(agent-name)/api) by configuring network or firewall rules.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
