dbcve.org
SubversionApplication · Jenkins

CVE-2020-2304

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-04
Fix available
A fix is available. Upgrade to after 2.13.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Subversion Plugin 2.13.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 confidence

The Jenkins Subversion Plugin versions 2.13.1 and earlier contains an XML parser that is not configured to prevent XML external entity (XXE) attacks. This vulnerability allows a remote attacker with the ability to supply crafted XML content to the plugin to potentially read internal files or cause denial of service via malicious external entity references.

MitigationUpgrade Jenkins Subversion Plugin to version 2.13.2 or later, which configures the XML parser to prevent XXE attacks. As a temporary workaround, restrict who can provide XML input to the plugin.

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
SubversionApplication
Affected:<= 2.13.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify installed Subversion Plugin version
    Go to Jenkins dashboard > Manage Jenkins > Manage Plugins > Installed tab and locate the Subversion Plugin, or check the plugin's .hpi file in the plugins directory for the version manifest
    Affected if Version is 2.13.1 or earlier
  2. Verify plugin is actively used
    Check Jenkins jobs for any using Subversion as their SCM (Source Code Management) configuration, or look for Subversion-related build steps in job configurations
    Affected if The Subversion Plugin is configured or used in any job definitions
  3. Assess XML input exposure
    Review which users or external systems can submit or influence XML content processed by the Subversion Plugin, such as SVN commit messages, repository metadata, or XML-based build triggers
    Affected if Untrusted users or external systems can supply XML input to the plugin without prior validation

You are affected if the Subversion Plugin version is 2.13.1 or earlier AND the plugin is in use where it processes XML content from untrusted sources.

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 2.13.1
Interim mitigation

Upgrade Jenkins Subversion Plugin to version 2.13.2 or later, which configures the XML parser to prevent XXE attacks. As a temporary workaround, restrict who can provide XML input to the plugin.

Fix this in Subversion Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2304 — 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-2304 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