Skip to content
Fencer Intel
high 7.5

CVE-2019-10337 json

Improper Restriction of XML External Entity Reference Jenkins Token Macro Plugin

published 7y ago modified 4mo ago also GHSA-g6h2-4x64-c59x , EUVD-2022-3903

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

An XML external entities (XXE) vulnerability in Jenkins Token Macro Plugin 2.7 and earlier allowed attackers able to control a the content of the input file for the "XML" macro to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.

Patch / fix

  • maven org.jenkins-ci.plugins:token-macro 2.8
  • atomic-openshift openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7
  • jenkins-2-plugins openshift 3.11 3.11.1560870549-1.el7
  • atomic-openshift-pod openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7
  • atomic-openshift-node openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7
  • atomic-openshift-tests openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7
  • atomic-openshift-master openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7
  • atomic-openshift-clients openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7
  • atomic-openshift-sdn-ovs openshift 3.11 3.11.129-1.git.0.bd4f2d5.el7

red hat advisories RHSA-2019:1851RHSA-2019:1636

Is CVE-2019-10337 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-2019-10337 updated cvss 6.5

jenkins-plugin-token-macro: XML External Entity processing the ${XML} macro

  • Red Hat OpenShift Container Platform 3.6 jenkins-plugin-token-macro Red Hat OpenShift Container Platform 3.7 jenkins-plugin-token-macro Red Hat OpenShift Container Platform 3.9 jenkins-plugin-token-macro Red Hat OpenShift Container Platform 3.10 jenkins-plugin-token-macro
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins 3.11.1560870549-1.el7, atomic-openshift 3.11.129-1.git.0.bd4f2d5.el7, atomic-openshift-pod 3.11.129-1.git.0.bd4f2d5.el7, atomic-openshift-node 3.11.129-1.git.0.bd4f2d5.el7, atomic-openshift-tests 3.11.129-1.git.0.bd4f2d5.el7, atomic-openshift-master 3.11.129-1.git.0.bd4f2d5.el7, +8 more
    fixed: vendor fix RHSA-2019:1851
  • Red Hat OpenShift Container Platform 4.1 jenkins-2-plugins 4.1.1561471763-1.el7
    fixed: vendor fix RHSA-2019:1636

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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:token-macro
<2.8
2.8

Affected products

  • Jenkins project Jenkins Token Macro 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.