Skip to content
Fencer Intel
critical 9.0

CVE-2017-7465 json

It was found that the JAXP implementation used in JBoss EAP 7.0 for XSLT processing is vulnerable to code injection.

published 2018-06-27 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16489

cvss
9.0
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

It was found that the JAXP implementation used in JBoss EAP 7.0 for XSLT processing is vulnerable to code injection. An attacker could use this flaw to cause remote code execution if they are able to provide XSLT content for parsing. Doing a transform in JAXP requires the use of a 'javax.xml.transform.TransformerFactory'. If the FEATURE_SECURE_PROCESSING feature is set to 'true', it mitigates this vulnerability.

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-7465 updated cvss 9.0

JBoss: JAXP in EAP 7.0 allows RCE via XSL

  • Red Hat JBoss Enterprise Application Platform 7 org.jboss.eap-jboss-eap-parent
    affected: workaround, no fix planned “Will not fix”
  • Red Hat EAP-CD 14 Tech Preview
    fixed: vendor fix RHSA-2020:2563
  • Red Hat JBoss Enterprise Web Server 3 tomcat Red Hat Mobile Application Platform 4 security
    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

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

CVSS scores

assigned by version score vector
CNA 3.0 9.0 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 3.0 9.8 CVSS:3.0/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

Affected products

  • [UNKNOWN] jboss

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference
  • CWE-94 Improper Control of Generation of Code

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.