Crap4jApplication · Jenkins
CVE-2023-28680
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 Crap4J Plugin 0.9 and earlier does not configure its XML parser to prevent XML external entity (XXE) 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 Crap4J Plugin version 0.9 and earlier uses an XML parser that is not configured to prevent XML External Entity (XXE) attacks. This allows attackers to submit specially crafted XML containing external entity references, potentially enabling disclosure of internal files, SSRF attacks, or 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
Crap4jApplication
<= 0.9CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Crap4J plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or list the contents of $JENKINS_HOME/plugins/ directory to see if crap4j folder existsAffected if The Crap4J plugin folder exists in the Jenkins plugins directory
-
Determine installed Crap4J plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and locate Crap4J in the list to read its version, or examine the plugin's manifest file at $JENKINS_HOME/plugins/crap4j/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if Unable to determine version or version field is missing from plugin metadata
-
Compare version against affected rangeCheck if the installed version is 0.9 or any version number less than 0.9 (e.g., 0.8, 0.7, etc.)Affected if The installed version is 0.9 or earlier (versions <= 0.9 are affected)
If the Crap4J plugin is installed and its version is 0.9 or earlier, the environment is vulnerable to XXE attacks via this plugin.
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.
dbcve · scopedConfigure the XML parser to disable external entity processing by setting the appropriate security features on the DocumentBuilderFactory (e.g., disabling DTDs and external entities in Java XML parsers).
Upgrade to a Crap4J plugin version greater than 0.9 (check Jenkins security advisory for exact fixed version)
- Identify the current Crap4J plugin version in use by navigating to Manage Jenkins > Manage Plugins > Installed
- Check the Jenkins plugin repository or Jenkins security advisory for the specific fixed version of Crap4J plugin that addresses CVE-2023-28680
- Upgrade the Crap4J plugin to the fixed version through Manage Plugins > Advanced > Upload Plugin or via the Update Center
- Restart Jenkins if required to complete the plugin installation
- Verify the upgrade was successful and the plugin functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Crap4j
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28680 — 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-2023-28680 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