dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2017-7465

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JBoss EAP 7.0 contains a code injection vulnerability in its JAXP implementation for XSLT processing. Attackers who can supply XSLT content for parsing can achieve remote code execution by exploiting the javax.xml.transform.TransformerFactory. The vulnerability is mitigated by enabling the FEATURE_SECURE_PROCESSING feature.

MitigationEnable FEATURE_SECURE_PROCESSING on all javax.xml.transform.TransformerFactory instances used for XSLT parsing to prevent code injection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JBoss EAP version
    Run 'jboss-cli.sh --version' or check the product.conf file in $JBOSS_HOME/bin to confirm the installed version is 7.0.0
    Affected if The installed JBoss EAP version is exactly 7.0.0
  2. Locate XSLT processing code
    Search deployed applications for usage of javax.xml.transform.TransformerFactory, javax.xml.transform.Templates, or related XSLT classes in JSP, servlet, or Java deployment archives
    Affected if Applications deployed on the server perform XSLT transformations using TransformerFactory
  3. Inspect TransformerFactory configuration
    Review application source code and configuration files for TransformerFactory instantiation - look for new javax.xml.transform.TransformerFactory calls and check if setAttribute("http://javax.xml.XMLConstants/feature/secure-processing", true) or equivalent is called
    Affected if TransformerFactory instances are created without FEATURE_SECURE_PROCESSING enabled via setAttribute or system property
  4. Check system property configuration
    Examine jboss startup scripts (standalone.conf or domain.conf) and application deployment descriptors for the system property javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING being set to true
    Affected if The secure processing feature is not enabled via system property or programmatically on the TransformerFactory

You are affected if you run JBoss EAP 7.0.0 and have applications that perform XSLT transformations using TransformerFactory without FEATURE_SECURE_PROCESSING enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable FEATURE_SECURE_PROCESSING on all javax.xml.transform.TransformerFactory instances used for XSLT parsing to prevent code injection attacks.

Recommended fix High confidence

JBoss EAP 7.0.1 or later (or migrate to newer EAP 7.x line such as 7.4)

  1. Locate the javax.xml.transform.TransformerFactory usage in the application's code that processes XSLT
  2. Add the following security feature to the TransformerFactory before processing any XSLT: transformerFactory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true)
  3. Alternatively, set the system property: System.setProperty(XMLConstants.FEATURE_SECURE_PROCESSING, "true")
  4. If using Saxon or other third-party XSLT processors, ensure FEATURE_SECURE_PROCESSING is enabled for those as well
  5. Verify that external entity (XXE) protection is working by testing with malicious XML/XSLT input
  6. Consult JBoss EAP documentation for application-specific XML parser configuration
Caveat Ensure any legitimate XSLT functionality that relies on external resources or dynamic evaluation still works after enabling secure processing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data