Klocwork AnalysisApplication · Jenkins
CVE-2020-2247
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 Klocwork Analysis Plugin 2020.2.1 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 Klocwork Analysis Plugin 2020.2.1 and earlier fails to configure its XML parser to prevent XML External Entity (XXE) attacks. This allows attackers to inject malicious XML content containing external entity references to potentially read local files or perform server-side request forgery (SSRF) against the Jenkins server.
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
Klocwork AnalysisApplication
<= 2020.2.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify Klocwork Analysis plugin installation and versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or use Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i klocwork. Record the version number displayed.Affected if Plugin is installed with version 2020.2.1 or earlier.
-
Confirm plugin is actively processing Klocwork reportsCheck Jenkins job configurations for builds using the Klocwork Analysis build step. Review job configuration pages or examine job config.xml files for presence of <klocwork> or related XML parsing build steps.Affected if The plugin is configured in any job to parse Klocwork analysis results.
-
Identify XML report input sourcesReview job configurations to determine if Klocwork reports are imported from untrusted or external sources. Check build logs for Klocwork report import operations that process XML content.Affected if The plugin imports or parses XML reports from build outputs or external servers.
-
Check for XXE-prone XML parser usageExamine Jenkins system logs and plugin debug output for XML parsing errors or behavior indicating external entity processing. Look for evidence of XML parser initialization in plugin code or documentation.Affected if The plugin processes XML without explicit XXE protection (DOCTYPE disallowing and external entity disabling not configured).
A user is affected if the Klocwork Analysis plugin version 2020.2.1 or earlier is installed and configured to parse Klocwork XML reports in any Jenkins job.
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 dataConfigure the XML parser to disable external entity processing by setting appropriate features such as disallowing DOCTYPE declarations and disabling external entities. Upgrade to a patched version if available.
Fix this in Klocwork Analysis
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2247 — 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-2020-2247 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