Summary
The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /queue/item/(ID)/api showed information about tasks in the queue (typically builds waiting to start). This included information about tasks that the current user otherwise has no access to, e.g. due to lack of Item/Read permission. This has been fixed, and the API endpoint is now only available for tasks that the current user has access to.
Impact
CVE-2017-1000399 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.73.2, 2.84); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.jenkins-ci.main:jenkins-core to 2.73.2 or later; org.jenkins-ci.main:jenkins-core to 2.84 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2017-1000399? CVE-2017-1000399 is a medium-severity security vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions <= 2.73.1. It is fixed in 2.73.2, 2.84.
- How severe is CVE-2017-1000399? CVE-2017-1000399 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2017-1000399? org.jenkins-ci.main:jenkins-core (maven) versions <= 2.73.1 is affected.
- Is there a fix for CVE-2017-1000399? Yes. CVE-2017-1000399 is fixed in 2.73.2, 2.84. Upgrade to this version or later.
- Is CVE-2017-1000399 exploitable, and should I be worried? Whether CVE-2017-1000399 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2017-1000399 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2017-1000399?
- Upgrade
org.jenkins-ci.main:jenkins-coreto 2.73.2 or later - Upgrade
org.jenkins-ci.main:jenkins-coreto 2.84 or later
- Upgrade