What is the severity of CVE-2019-10458?

CVE-2019-10458 has a medium severity rating, threatening the security of Jenkins installations by allowing arbitrary code execution.

How do I fix CVE-2019-10458?

To fix CVE-2019-10458, upgrade Jenkins Puppet Enterprise Pipeline to version 1.3.2 or later, which addresses the vulnerability.

What are the potential impacts of CVE-2019-10458?

The potential impacts of CVE-2019-10458 include unauthorized access to sensitive data and the ability to execute arbitrary code on the Jenkins server.

Who is affected by CVE-2019-10458?

CVE-2019-10458 affects users of Jenkins Puppet Enterprise Pipeline version 1.3.1 and earlier.

When was CVE-2019-10458 disclosed?

CVE-2019-10458 was disclosed on October 16, 2019.

Vulnerability/
CVE-2019-10458

critical

9.9

CWE

183

16/10/2019

4/8/2024

CVE-2019-10458

First published: Wed Oct 16 2019(Updated: )

Jenkins Puppet Enterprise Pipeline 1.3.1 and earlier specifies unsafe values in its custom Script Security whitelist, allowing attackers able to execute Script Security protected scripts to execute arbitrary code.

Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Puppet Enterprise Pipeline	<=1.3.1

Never miss a vulnerability like this again

Reference Links

https://jenkins.io/security/advisory/2019-10-16/#SECURITY-918

Frequently Asked Questions

What is the severity of CVE-2019-10458?
CVE-2019-10458 has a medium severity rating, threatening the security of Jenkins installations by allowing arbitrary code execution.
How do I fix CVE-2019-10458?
To fix CVE-2019-10458, upgrade Jenkins Puppet Enterprise Pipeline to version 1.3.2 or later, which addresses the vulnerability.
What are the potential impacts of CVE-2019-10458?
The potential impacts of CVE-2019-10458 include unauthorized access to sensitive data and the ability to execute arbitrary code on the Jenkins server.
Who is affected by CVE-2019-10458?
CVE-2019-10458 affects users of Jenkins Puppet Enterprise Pipeline version 1.3.1 and earlier.
When was CVE-2019-10458 disclosed?
CVE-2019-10458 was disclosed on October 16, 2019.

collector/nvd-index
collector/nvd-api
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/last-modified-date
agent/references
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/jenkins
canonical/jenkins puppet enterprise pipeline
version/jenkins puppet enterprise pipeline/1.3.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-2019-10458?
CVE-2019-10458 has a medium severity rating, threatening the security of Jenkins installations by allowing arbitrary code execution.
How do I fix CVE-2019-10458?
To fix CVE-2019-10458, upgrade Jenkins Puppet Enterprise Pipeline to version 1.3.2 or later, which addresses the vulnerability.
What are the potential impacts of CVE-2019-10458?
The potential impacts of CVE-2019-10458 include unauthorized access to sensitive data and the ability to execute arbitrary code on the Jenkins server.
Who is affected by CVE-2019-10458?
CVE-2019-10458 affects users of Jenkins Puppet Enterprise Pipeline version 1.3.1 and earlier.
When was CVE-2019-10458 disclosed?
CVE-2019-10458 was disclosed on October 16, 2019.