Skip to content
Fencer Intel
high 7.1

CVE-2020-2138 json

XXE vulnerability in Jenkins Cobertura Plugin

published 6y ago modified 4mo ago also GHSA-vpfj-5gg5-fvfm , EUVD-2022-5393

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

Jenkins Cobertura Plugin 1.15 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

Patch / fix

  • maven org.jenkins-ci.plugins:cobertura 1.16

Is CVE-2020-2138 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-2138 updated cvss 5.4

jenkins-cobertura-plugin: XML parser not configured to prevent XXE attack

  • Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins Red Hat OpenShift Container Platform 4 jenkins-2-plugins
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:cobertura
<1.16
1.16

Affected products

  • Jenkins project Jenkins Cobertura Plugin

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.