What is the severity of CVE-2018-1000009?

CVE-2018-1000009 has a high severity rating due to its potential to allow attackers to extract sensitive information from the Jenkins master.

How do I fix CVE-2018-1000009?

To fix CVE-2018-1000009, upgrade the Jenkins Checkstyle Plugin to version 3.50 or later.

Who is affected by CVE-2018-1000009?

CVE-2018-1000009 affects users of Jenkins with the Checkstyle Plugin version 3.49 and earlier.

What types of attacks can occur due to CVE-2018-1000009?

CVE-2018-1000009 can enable secret extraction, server-side request forgery, and denial-of-service attacks.

Is there a workaround for CVE-2018-1000009?

There isn't a specific workaround for CVE-2018-1000009; the best action is to upgrade the affected plugin.

Vulnerability/
CVE-2018-1000009

high

8.8

CWE

611

23/1/2018

14/5/2022

16/9/2024

CVE-2018-1000009: XEE

First published: Tue Jan 23 2018(Updated: )

Jenkins Checkstyle Plugin 3.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
maven/org.jvnet.hudson.plugins:checkstyle	<3.50	3.50
Checkstyle	<=3.49

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-1000009?
CVE-2018-1000009 has a high severity rating due to its potential to allow attackers to extract sensitive information from the Jenkins master.
How do I fix CVE-2018-1000009?
To fix CVE-2018-1000009, upgrade the Jenkins Checkstyle Plugin to version 3.50 or later.
Who is affected by CVE-2018-1000009?
CVE-2018-1000009 affects users of Jenkins with the Checkstyle Plugin version 3.49 and earlier.
What types of attacks can occur due to CVE-2018-1000009?
CVE-2018-1000009 can enable secret extraction, server-side request forgery, and denial-of-service attacks.
Is there a workaround for CVE-2018-1000009?
There isn't a specific workaround for CVE-2018-1000009; the best action is to upgrade the affected plugin.

agent/type
collector/github-advisory-latest
source/GitHub
alias/GHSA-jfj9-7j5w-6xgx
alias/CVE-2018-1000009
agent/software-canonical-lookup
agent/weakness
agent/severity
agent/references
agent/description
agent/author
agent/softwarecombine
collector/github-advisory
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/trending
agent/source
agent/tags
collector/nvd-cve
source/NVD
agent/software-canonical-lookup-request
collector/nvd-index
package-manager/maven
vendor/jenkins
canonical/checkstyle
version/checkstyle/3.49

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.