What is the severity of CVE-2017-1000356?

CVE-2017-1000356 has been rated as high severity due to the potential for unauthorized account creation and admin user deletion.

How do I fix CVE-2017-1000356?

To fix CVE-2017-1000356, upgrade Jenkins to version 2.60 or later, or 2.46.2 LTS or later.

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

CVE-2017-1000356 affects Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier.

What impact could CVE-2017-1000356 have on my Jenkins installation?

CVE-2017-1000356 could allow an attacker to create a new user account, potentially compromising the existing administrative controls.

Is there a way to mitigate CVE-2017-1000356 without upgrading?

There are no direct mitigations available without upgrading, as the vulnerability relies on the software's inherent user account creation functionality.

Vulnerability/
CVE-2017-1000356

high

8.8

CWE

352

29/1/2018

5/8/2024

CVE-2017-1000356: CSRF

First published: Mon Jan 29 2018(Updated: )

Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an issue in the Jenkins user database authentication realm: create an account if signup is enabled; or create an account if the victim is an administrator, possibly deleting the existing default admin user in the process and allowing a wide variety of impacts.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Jenkins Jenkins	<=2.56
Jenkins Jenkins	<=2.46.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1000356?
CVE-2017-1000356 has been rated as high severity due to the potential for unauthorized account creation and admin user deletion.
How do I fix CVE-2017-1000356?
To fix CVE-2017-1000356, upgrade Jenkins to version 2.60 or later, or 2.46.2 LTS or later.
What versions of Jenkins are affected by CVE-2017-1000356?
CVE-2017-1000356 affects Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier.
What impact could CVE-2017-1000356 have on my Jenkins installation?
CVE-2017-1000356 could allow an attacker to create a new user account, potentially compromising the existing administrative controls.
Is there a way to mitigate CVE-2017-1000356 without upgrading?
There are no direct mitigations available without upgrading, as the vulnerability relies on the software's inherent user account creation functionality.

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

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-1000356?
CVE-2017-1000356 has been rated as high severity due to the potential for unauthorized account creation and admin user deletion.
How do I fix CVE-2017-1000356?
To fix CVE-2017-1000356, upgrade Jenkins to version 2.60 or later, or 2.46.2 LTS or later.
What versions of Jenkins are affected by CVE-2017-1000356?
CVE-2017-1000356 affects Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier.
What impact could CVE-2017-1000356 have on my Jenkins installation?
CVE-2017-1000356 could allow an attacker to create a new user account, potentially compromising the existing administrative controls.
Is there a way to mitigate CVE-2017-1000356 without upgrading?
There are no direct mitigations available without upgrading, as the vulnerability relies on the software's inherent user account creation functionality.