WarningsApplication · Jenkins
CVE-2018-1000012
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 Warnings Plugin 4.64 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 confidenceJenkins Warnings Plugin versions 4.64 and earlier are vulnerable to XML External Entity (XXE) injection. The plugin processes XML files parsed during the build process without disabling external entities, allowing authenticated Jenkins users to craft malicious XML files that can extract secrets from the Jenkins master, perform SSRF attacks against internal systems, 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
WarningsApplication
<= 4.64CVSS 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.
-
Verify Jenkins Warnings Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Warnings' or 'Warnings Next Generation' plugin, or list contents of $JENKINS_HOME/plugins/ directoryAffected if The Warnings plugin is present in the Jenkins plugins directory
-
Determine the installed version of Jenkins Warnings PluginIn the Installed Plugins table, locate the Warnings plugin and record the Version column, or inspect the plugin manifest at $JENKINS_HOME/plugins/warnings/META-INF/MANIFEST.MFAffected if The installed version is 4.64 or earlier
-
Identify if XML-based parsers are configured in build jobsReview Jenkins job configurations for build steps that use the Warnings Plugin with XML parsers - look for 'Console Parsers' or 'Parser Configuration' settings that reference XML-based parsers, or inspect job config.xml files for <parser> elementsAffected if Build jobs are configured to parse XML files using the Warnings Plugin
-
Inspect build pipelines for XML file processingExamine Jenkinsfiles and job configurations for any step that passes XML files to the Warnings Plugin, including XML reports generated during builds or uploaded as artifactsAffected if Build jobs process XML files through the Warnings Plugin from any source
A Jenkins instance is affected if the Warnings Plugin version 4.64 or earlier is installed AND the plugin is actively parsing XML files in any build job configuration.
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 Jenkins Warnings Plugin to version 5.0 or later, which disables external entity processing. Until patched, restrict or disable the plugin's XML parsing features and review build pipelines for untrusted XML inputs.
Fix this in Warnings
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-1000012 — 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-1000012 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