PmdApplication · Jenkins
CVE-2018-1000008
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins PMD 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins PMD Plugin versions 3.49 and earlier is vulnerable to XML External Entity (XXE) injection. The plugin processes XML files during build analysis without disabling external entity resolution, allowing authenticated users with build permissions to inject malicious entity references in XML files. This enables attackers to read arbitrary files from the Jenkins master, perform SSRF attacks against internal services, or cause denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PmdApplication
<= 3.49CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PMD Plugin installation statusUse Jenkins Script Console to list installed plugins: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'pmd') { println "PMD Plugin: ${it.displayName} - Version: ${it.version}" } }Affected if PMD Plugin is installed and version is 3.49 or earlier
-
Verify PMD Plugin versionCompare the installed version number to the affected range: 3.49 and earlier. The version displays in Manage Jenkins > Manage Plugins > Installed tab, or via the script above.Affected if Installed version is 3.49 or lower
-
Identify jobs using PMD analysisSearch job configurations for the PMD build step. Using Jenkins CLI: jenkins-cli.jar or Script Console to search: Jenkins.instance.allItems.findAll { it instanceof hudson.model.FreeStyleProject || it instanceof org.jenkinsci.plugins.workflow.job.WorkflowJob }.findAll { it.builders.any { it.class.name.contains('Pmd') } }.collect { it.fullName }Affected if Jobs are configured to run PMD analysis, as the vulnerability only triggers when the plugin processes XML files during build analysis
-
Locate XML files processed by PMDReview build configurations and workspace files to identify XML input files that PMD processes. Check job configuration XML files or the 'pmd' build step configuration for file patterns (e.g., *.xml)Affected if PMD is configured to analyze XML files, which is the attack surface for XXE injection
You are affected if the PMD Plugin version is 3.49 or earlier AND the plugin is actively configured to analyze XML files in any build job.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade PMD Plugin to version 3.50 or later which disables external entity processing. If immediate upgrade is not possible, restrict XML file inputs in build pipelines and monitor for suspicious build activity involving XML files.
Fix this in Pmd
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data