Pom2configApplication · Jenkins
CVE-2021-43576
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 pom2config Plugin 1.2 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks, allowing attackers with Overall/Read and Item/Read permissions to have Jenkins parse a crafted XML file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.
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 pom2config Plugin versions 1.2 and earlier contains an XML External Entity (XXE) vulnerability because its XML parser is not configured to disable external entity processing. Attackers with Overall/Read and Item/Read permissions can supply a crafted XML file containing malicious external entity references to extract secrets from the Jenkins controller or perform server-side request forgery (SSRF).
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
Pom2configApplication
<= 1.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check if pom2config plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'pom2config', or run: jenkins-plugin-cli --list-plugins | grep pom2configAffected if The plugin appears in the installed plugins list
-
Verify the installed versionIn the Installed plugins tab, find the Version column for pom2config, or check the plugin's manifest (pom2config.jpi or pom2config.hpi file in JENKINS_HOME/plugins/)Affected if Version is 1.2 or any version lower than 1.2
-
Confirm plugin is enabled and loadedCheck that the plugin is not disabled in JENKINS_HOME/jenkins.install.UpgradeWizard.state or via Manage Jenkins > Manage Plugins > Advanced settingsAffected if Plugin status shows as Enabled or Active
-
Check for configured jobs using pom2configInspect job configurations that may reference the pom2config functionality, typically in build scripts or pre-build steps that invoke the plugin's XML processingAffected if Any job configuration references pom2config and processes XML files as input
You are affected if the pom2config plugin version 1.2 or lower is installed and enabled, and your jobs use the plugin to process XML files with the default XML parser settings.
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 dataThe plugin's XML parser must be configured to prevent XXE by disabling external entity and external DTD access, typically by setting features like XMLConstants.ACCESS_EXTERNAL_DTD and XMLConstants.ACCESS_EXTERNAL_SCHEMA to empty strings, or enabling secure processing features.
Fix this in Pom2config
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43576 — 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-2021-43576 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