XXE in Apache Commons Jelly
CVE-2017-12621
- CVSS v3
- 9.8 Critical
- Public exploits
- None known
- EPSS
- 0.081 · 95.0th percentile
- Published
- 2017-09-28
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.
Vulnerability class: XXE (XML External Entity)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.081, 95.0th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Apache Commons Jelly
- Apache Software Foundation Commons Jelly — versions 1.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 3 other repositories (ARPSyndicate/cvemon, chtompki/from-no-oss-contributions-to-pmc, chtompki/getting-started-with-oss). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- issues.apache.org/jira/browse/JELLY-293 (Patch, Issue Tracking, Vendor Advisory)
- [dev] 20170927 [SECURITY] CVE-2017-12621 Apache Commons Jelly connects to URL with custom doctype definitions. (mailing-list)
- www.securityfocus.com/bid/101052 (Third Party Advisory, VDB Entry, vdb-entry)
- www.securitytracker.com/id/1039444 (Third Party Advisory, VDB Entry, vdb-entry)