dbcve.org
ValgrindApplication · Jenkins

CVE-2020-2245

HIGH · 7.1 CVSS v3.1 Published 2020-09-01
Fix available
A fix is available. Upgrade to after 0.28 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Jenkins Valgrind Plugin 0.28 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 confidence

Jenkins Valgrind Plugin version 0.28 and earlier does not configure its XML parser to prevent XML External Entity (XXE) attacks, allowing an attacker to inject malicious external entity references into parsed XML input processed by the plugin.

MitigationUpgrade Jenkins Valgrind Plugin to version 0.29 or later which includes proper XML parser configuration to disable external entity processing.

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
ValgrindApplication
Affected:<= 0.28

CVSS 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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Jenkins Valgrind Plugin
    In the Jenkins web interface, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Valgrind' in the list of installed plugins, or check the plugin manifest file in $JENKINS_HOME/plugins/valgrind/
    Affected if The Valgrind plugin is present in the Jenkins environment
  2. Identify the installed version
    In the Jenkins plugin manager, click on the Valgrind plugin entry to view its version number, or read the version from the plugin's manifest.json or .hpi file in $JENKINS_HOME/plugins/valgrind/
    Affected if The version displayed is 0.28 or an earlier version number
  3. Confirm XXE exposure
    Verify the plugin is actively used in any Jenkins jobs by checking job configurations for 'Publish Valgrind results' or 'Valgrind' build steps, or by inspecting any configured Valgrind XML result files being processed
    Affected if The plugin processes XML files from Valgrind reports and the version is 0.28 or earlier

The environment is affected if Jenkins Valgrind Plugin version 0.28 or earlier is installed and is used to parse Valgrind XML results.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 0.28
Interim mitigation

Upgrade Jenkins Valgrind Plugin to version 0.29 or later which includes proper XML parser configuration to disable external entity processing.

Fix this in Valgrind Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2245 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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