CcmApplication · Jenkins
CVE-2018-1000054
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 CCM Plugin 3.1 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 CCM Plugin versions 3.1 and earlier contains an XML External Entity (XXE) injection vulnerability. The plugin processes XML files during build parsing without disabling external entity resolution, allowing authenticated users to inject malicious XML that can read local files from the Jenkins master, perform SSRF attacks by making arbitrary HTTP requests from the server, or cause denial of service through recursive entity expansion.
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
CcmApplication
<= 3.1CVSS 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
- Low
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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.
-
Check if the CCM plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'CCM' or 'CCM Plugin' in the list of installed pluginsAffected if The CCM plugin appears in the installed plugins list
-
Identify the CCM plugin versionIn the installed plugins list, locate the CCM plugin and note the Version column entry, or click on the plugin to view its details page where the version is displayedAffected if The version listed is 3.1 or any version lower than 3.1 (e.g., 3.0, 2.x, 1.x)
-
Check if CCM builds are being performedReview your Jenkins jobs to see if any jobs use the CCM plugin as a build step or post-build action, or check build logs for 'CCM' or 'ccm' entries indicating the plugin is processing buildsAffected if Any Jenkins jobs are configured to run CCM builds or the plugin is actively parsing build results containing CCM XML output
You are affected if the CCM plugin is installed with version 3.1 or earlier AND you have jobs that trigger the plugin to process XML files during build parsing.
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 the CCM Plugin to a version after 3.1 that includes XXE protection, or implement XML parser configuration to disable external entity processing if upgrading is not immediately feasible. Review and rotate any credentials or secrets that may have been exposed.
Fix this in Ccm
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000054 — 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-1000054 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