What is the severity of CVE-2017-1000400?

CVE-2017-1000400 is considered a moderate severity vulnerability due to unauthorized information disclosure.

How do I fix CVE-2017-1000400?

To fix CVE-2017-1000400, upgrade Jenkins to version 2.73.2 or later, or version 2.83.1 or later.

What kind of information is exposed by CVE-2017-1000400?

CVE-2017-1000400 exposes information about upstream and downstream projects that the user normally wouldn't have access to.

Which versions of Jenkins are affected by CVE-2017-1000400?

Jenkins versions 2.73.1 and earlier, and 2.83 and earlier are affected by CVE-2017-1000400.

Was CVE-2017-1000400 publicly disclosed?

Yes, CVE-2017-1000400 was publicly disclosed and a fix was provided in subsequent Jenkins releases.

Vulnerability/
CVE-2017-1000400

medium

4.3

CWE

862

26/1/2018

5/8/2024

CVE-2017-1000400

First published: Fri Jan 26 2018(Updated: )

The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /job/(job-name)/api contained information about upstream and downstream projects. 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 now only lists upstream and downstream projects that the current user has access to.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Jenkins Jenkins	<=2.73.1
Jenkins Jenkins	<=2.83

Never miss a vulnerability like this again

Reference Links

https://jenkins.io/security/advisory/2017-10-11/

Frequently Asked Questions

What is the severity of CVE-2017-1000400?
CVE-2017-1000400 is considered a moderate severity vulnerability due to unauthorized information disclosure.
How do I fix CVE-2017-1000400?
To fix CVE-2017-1000400, upgrade Jenkins to version 2.73.2 or later, or version 2.83.1 or later.
What kind of information is exposed by CVE-2017-1000400?
CVE-2017-1000400 exposes information about upstream and downstream projects that the user normally wouldn't have access to.
Which versions of Jenkins are affected by CVE-2017-1000400?
Jenkins versions 2.73.1 and earlier, and 2.83 and earlier are affected by CVE-2017-1000400.
Was CVE-2017-1000400 publicly disclosed?
Yes, CVE-2017-1000400 was publicly disclosed and a fix was provided in subsequent Jenkins releases.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/weakness
agent/last-modified-date
agent/author
agent/description
agent/tags
agent/event
agent/first-publish-date
agent/source
vendor/jenkins
canonical/jenkins jenkins
version/jenkins jenkins/2.73.1
version/jenkins jenkins/2.83

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-1000400?
CVE-2017-1000400 is considered a moderate severity vulnerability due to unauthorized information disclosure.
How do I fix CVE-2017-1000400?
To fix CVE-2017-1000400, upgrade Jenkins to version 2.73.2 or later, or version 2.83.1 or later.
What kind of information is exposed by CVE-2017-1000400?
CVE-2017-1000400 exposes information about upstream and downstream projects that the user normally wouldn't have access to.
Which versions of Jenkins are affected by CVE-2017-1000400?
Jenkins versions 2.73.1 and earlier, and 2.83 and earlier are affected by CVE-2017-1000400.
Was CVE-2017-1000400 publicly disclosed?
Yes, CVE-2017-1000400 was publicly disclosed and a fix was provided in subsequent Jenkins releases.