What is the severity of CVE-2018-1000010?

CVE-2018-1000010 has a high severity rating due to its potential to allow attackers to access sensitive information and execute denial-of-service attacks.

How do I fix CVE-2018-1000010?

To fix CVE-2018-1000010, upgrade the Jenkins DRY Plugin to version 2.50 or later.

Which versions of Jenkins are affected by CVE-2018-1000010?

CVE-2018-1000010 affects Jenkins DRY Plugin versions 2.49 and earlier.

What impact does CVE-2018-1000010 have on Jenkins security?

CVE-2018-1000010 can lead to the leak of sensitive information and enable server-side request forgery.

Are there any workarounds for CVE-2018-1000010 if I cannot upgrade Jenkins?

There are no known workarounds for CVE-2018-1000010; updating to the fixed version is necessary.

Vulnerability/
CVE-2018-1000010

high

8.8

CWE

611

23/1/2018

14/5/2022

3/10/2022

5/8/2024

CVE-2018-1000010: XEE

First published: Tue Jan 23 2018(Updated: )

Jenkins DRY Plugin 2.49 and earlier processes XML external entities in files it parses as part of the build process, allowing attackers with user permissions in Jenkins to extract secrets from the Jenkins master, perform server-side request forgery, or denial-of-service attacks.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Jenkins Dry	<=2.49
maven/org.jvnet.hudson.plugins:dry	<=2.49	2.50
	<=2.49

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-1000010?
CVE-2018-1000010 has a high severity rating due to its potential to allow attackers to access sensitive information and execute denial-of-service attacks.
How do I fix CVE-2018-1000010?
To fix CVE-2018-1000010, upgrade the Jenkins DRY Plugin to version 2.50 or later.
Which versions of Jenkins are affected by CVE-2018-1000010?
CVE-2018-1000010 affects Jenkins DRY Plugin versions 2.49 and earlier.
What impact does CVE-2018-1000010 have on Jenkins security?
CVE-2018-1000010 can lead to the leak of sensitive information and enable server-side request forgery.
Are there any workarounds for CVE-2018-1000010 if I cannot upgrade Jenkins?
There are no known workarounds for CVE-2018-1000010; updating to the fixed version is necessary.

collector/nvd-index
agent/type
agent/first-publish-date
collector/github-advisory-latest
source/GitHub
alias/GHSA-x7qf-qh3r-mx22
alias/CVE-2018-1000010
agent/software-canonical-lookup
agent/weakness
agent/severity
agent/references
agent/description
agent/author
agent/softwarecombine
collector/nvd-cve
source/NVD
collector/github-advisory
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins dry
version/jenkins dry/2.49
package-manager/maven

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.