Skip to content
Fencer Intel
critical 9.8

CVE-2017-12621 json

Improper Restriction of XML External Entity Reference in Jelly

published 9y ago modified last mo. also GHSA-6g33-82gc-3pw5 , EUVD-2022-2787

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

Summary

During Jelly (xml) file parsing with Apache Xerces, if a custom doctype entity is declared with a "SYSTEM" entity with a URL and that entity is used in the body of the Jelly file, during parser instantiation the parser will attempt to connect to said URL. This could lead to XML External Entity (XXE) attacks in Apache Commons Jelly before 1.0.1.

Patch / fix

  • maven commons-jelly:commons-jelly 1.0.1
  • apache commons_jelly 1.0.1

Is CVE-2017-12621 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-2017-12621 updated cvss 9.8

commons-jelly: Apache Commons Jelly connects to URL with custom doctype definitions

  • Red Hat OpenShift Container Platform 3.11 jenkins Red Hat OpenShift Container Platform 4 jenkins
    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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven commons-jelly:commons-jelly
<1.0.1
1.0.1

Affected products

  • Apache Software Foundation Apache Commons Jelly

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.