What is the severity of CVE-2017-1000398?

CVE-2017-1000398 has been rated as a high-severity vulnerability due to its potential exposure of sensitive information.

How do I fix CVE-2017-1000398?

To fix CVE-2017-1000398, you should upgrade Jenkins to version 2.73.2 or 2.83.1 or later.

What does CVE-2017-1000398 affect?

CVE-2017-1000398 affects Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier.

What kind of information does CVE-2017-1000398 expose?

CVE-2017-1000398 exposes information about tasks currently running on Jenkins agents that users should not have access to.

Can CVE-2017-1000398 lead to unauthorized access?

Yes, CVE-2017-1000398 can lead to unauthorized access to build information due to improper permission checks.

Vulnerability/
CVE-2017-1000398

medium

4.3

CWE

200

26/1/2018

5/8/2024

CVE-2017-1000398: Infoleak

First published: Fri Jan 26 2018(Updated: )

The remote API in Jenkins 2.73.1 and earlier, 2.83 and earlier at /computer/(agent-name)/api showed information about tasks (typically builds) currently running on that agent. 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 shows information about accessible tasks.

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-1000398?
CVE-2017-1000398 has been rated as a high-severity vulnerability due to its potential exposure of sensitive information.
How do I fix CVE-2017-1000398?
To fix CVE-2017-1000398, you should upgrade Jenkins to version 2.73.2 or 2.83.1 or later.
What does CVE-2017-1000398 affect?
CVE-2017-1000398 affects Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier.
What kind of information does CVE-2017-1000398 expose?
CVE-2017-1000398 exposes information about tasks currently running on Jenkins agents that users should not have access to.
Can CVE-2017-1000398 lead to unauthorized access?
Yes, CVE-2017-1000398 can lead to unauthorized access to build information due to improper permission checks.

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-1000398?
CVE-2017-1000398 has been rated as a high-severity vulnerability due to its potential exposure of sensitive information.
How do I fix CVE-2017-1000398?
To fix CVE-2017-1000398, you should upgrade Jenkins to version 2.73.2 or 2.83.1 or later.
What does CVE-2017-1000398 affect?
CVE-2017-1000398 affects Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier.
What kind of information does CVE-2017-1000398 expose?
CVE-2017-1000398 exposes information about tasks currently running on Jenkins agents that users should not have access to.
Can CVE-2017-1000398 lead to unauthorized access?
Yes, CVE-2017-1000398 can lead to unauthorized access to build information due to improper permission checks.