What is the severity of CVE-2017-1000393?

CVE-2017-1000393 is classified as a high severity vulnerability.

How do I fix CVE-2017-1000393?

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

Who is affected by CVE-2017-1000393?

CVE-2017-1000393 affects Jenkins versions 2.73.1 and earlier, and 2.83 and earlier.

What types of attacks can occur due to CVE-2017-1000393?

CVE-2017-1000393 can allow attackers to execute arbitrary shell commands on the Jenkins master node.

Can I disable the launch method to mitigate CVE-2017-1000393?

Disabling the 'Launch agent via execution of command on master' method can reduce exposure until a fix is applied.

Vulnerability/
CVE-2017-1000393

critical

CWE

26/1/2018

5/8/2024

CVE-2017-1000393: OS Command Injection

First published: Fri Jan 26 2018(Updated: )

Jenkins 2.73.1 and earlier, 2.83 and earlier users with permission to create or configure agents in Jenkins could configure a launch method called 'Launch agent via execution of command on master'. This allowed them to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of this launch method now requires the Run Scripts permission typically only granted to administrators.

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-1000393?
CVE-2017-1000393 is classified as a high severity vulnerability.
How do I fix CVE-2017-1000393?
To fix CVE-2017-1000393, upgrade Jenkins to version 2.73.2 or later, or 2.83.1 or later.
Who is affected by CVE-2017-1000393?
CVE-2017-1000393 affects Jenkins versions 2.73.1 and earlier, and 2.83 and earlier.
What types of attacks can occur due to CVE-2017-1000393?
CVE-2017-1000393 can allow attackers to execute arbitrary shell commands on the Jenkins master node.
Can I disable the launch method to mitigate CVE-2017-1000393?
Disabling the 'Launch agent via execution of command on master' method can reduce exposure until a fix is applied.

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-1000393?
CVE-2017-1000393 is classified as a high severity vulnerability.
How do I fix CVE-2017-1000393?
To fix CVE-2017-1000393, upgrade Jenkins to version 2.73.2 or later, or 2.83.1 or later.
Who is affected by CVE-2017-1000393?
CVE-2017-1000393 affects Jenkins versions 2.73.1 and earlier, and 2.83 and earlier.
What types of attacks can occur due to CVE-2017-1000393?
CVE-2017-1000393 can allow attackers to execute arbitrary shell commands on the Jenkins master node.
Can I disable the launch method to mitigate CVE-2017-1000393?
Disabling the 'Launch agent via execution of command on master' method can reduce exposure until a fix is applied.