What is the severity of CVE-2017-1000396?

CVE-2017-1000396 has been rated as a high severity vulnerability due to its potential for man-in-the-middle attacks.

How do I fix CVE-2017-1000396?

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

What versions of Jenkins are affected by CVE-2017-1000396?

Jenkins versions up to 2.73.1 and 2.83 are affected by CVE-2017-1000396.

What kind of attacks can CVE-2017-1000396 lead to?

CVE-2017-1000396 can lead to man-in-the-middle attacks due to incorrect SSL certificate verification.

Is CVE-2017-1000396 related to any libraries used in Jenkins?

Yes, CVE-2017-1000396 is linked to the commons-httpclient library bundled with certain Jenkins versions.

Vulnerability/
CVE-2017-1000396

medium

5.9

CWE

295

26/1/2018

5/8/2024

CVE-2017-1000396

First published: Fri Jan 26 2018(Updated: )

Jenkins 2.73.1 and earlier, 2.83 and earlier bundled a version of the commons-httpclient library with the vulnerability CVE-2012-6153 that incorrectly verified SSL certificates, making it susceptible to man-in-the-middle attacks. This library is widely used as a transitive dependency in Jenkins plugins. The fix for CVE-2012-6153 was backported to the version of commons-httpclient that is bundled in core and made available to plugins.

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-1000396?
CVE-2017-1000396 has been rated as a high severity vulnerability due to its potential for man-in-the-middle attacks.
How do I fix CVE-2017-1000396?
To fix CVE-2017-1000396, upgrade Jenkins to version 2.73.2 or 2.83.1 or later.
What versions of Jenkins are affected by CVE-2017-1000396?
Jenkins versions up to 2.73.1 and 2.83 are affected by CVE-2017-1000396.
What kind of attacks can CVE-2017-1000396 lead to?
CVE-2017-1000396 can lead to man-in-the-middle attacks due to incorrect SSL certificate verification.
Is CVE-2017-1000396 related to any libraries used in Jenkins?
Yes, CVE-2017-1000396 is linked to the commons-httpclient library bundled with certain Jenkins versions.

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-1000396?
CVE-2017-1000396 has been rated as a high severity vulnerability due to its potential for man-in-the-middle attacks.
How do I fix CVE-2017-1000396?
To fix CVE-2017-1000396, upgrade Jenkins to version 2.73.2 or 2.83.1 or later.
What versions of Jenkins are affected by CVE-2017-1000396?
Jenkins versions up to 2.73.1 and 2.83 are affected by CVE-2017-1000396.
What kind of attacks can CVE-2017-1000396 lead to?
CVE-2017-1000396 can lead to man-in-the-middle attacks due to incorrect SSL certificate verification.
Is CVE-2017-1000396 related to any libraries used in Jenkins?
Yes, CVE-2017-1000396 is linked to the commons-httpclient library bundled with certain Jenkins versions.