FindbugsApplication · Jenkins
CVE-2018-1000011
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 FindBugs Plugin 4.71 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 FindBugs Plugin versions 4.71 and earlier processes XML files using insecure XML parsing that allows XML External Entity (XXE) injection. Attackers with user-level permissions can exploit this vulnerability to read arbitrary files from the Jenkins master, perform server-side request forgery (SSRF) attacks, or cause denial of service by crafting malicious XML payloads in build-related files.
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
FindbugsApplication
<= 4.71CVSS 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 FindBugs plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: jenkins-cli.jar get-plugins. Look for 'FindBugs' in the list of installed plugins.Affected if The FindBugs plugin is not listed in installed plugins (not affected).
-
Determine the installed versionIn the Manage Plugins > Installed tab, locate the FindBugs plugin and note the version number displayed in the 'Version' column.Affected if The version is 4.71 or lower (for example, 4.71, 4.70, 4.68). Compare your version to the affected range: <= 4.71.
-
Confirm the plugin is enabledGo to Manage Jenkins > Manage Plugins > Installed tab, ensure FindBugs is not disabled, or check Manage Jenkins > Configure Global Security to verify plugin access is not restricted.Affected if The plugin is installed, enabled, and accessible to users with overall/read permissions.
-
Check for jobs using FindBugs analysisReview Jenkins jobs that utilize the 'FindBugs' post-build action or pipeline step, as the vulnerability triggers when the plugin parses XML files from build artifacts.Affected if Any active job is configured to run FindBugs analysis and process resulting XML report files.
You are affected if the FindBugs plugin version is 4.71 or earlier AND the plugin is installed and enabled in Jenkins, as the vulnerability requires the plugin to be present to process malicious XML payloads.
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 FindBugs Plugin to a version newer than 4.71 that disables external entity processing in XML parsing, or disable/uninstall the plugin if not needed.
Fix this in Findbugs
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.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-1000011 — 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-1000011 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