dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2017-7464

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-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 SAX and DOM parsing is vulnerable to certain XXE flaws. An attacker could use this flaw to cause DoS, SSRF, or information disclosure if they are able to provide XML content for parsing.

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

XXE (XML External Entity) injection vulnerability in the JAXP SAX and DOM parser implementation in JBoss EAP 7.0. An attacker who can supply malicious XML content for parsing can exploit unsanitized external entity processing to cause denial of service, perform SSRF attacks, or disclose sensitive information.

MitigationUpdate JBoss EAP 7.0 to a patched version that addresses the XXE vulnerability in JAXP, or configure XML parsers to disable external entity processing.

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

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 installation and version
    Run 'rpm -q jboss-eap' or check the installation directory for version files (e.g., $JBOSS_HOME/bin/version.sh)
    Affected if The installed version is exactly 7.0 (specifically 7.0.0)
  2. Locate JAXP parser usage in deployed applications
    Search WAR/EAR deployments for Java code using javax.xml.parsers.SAXParser or DocumentBuilder, or inspect application logs for XML parsing activity
    Affected if Applications use SAXParser or DocumentBuilder to process XML input from untrusted sources
  3. Determine if XML input sources are untrusted
    Review application code or configuration for XML parsing endpoints that accept external input (REST/SOAP APIs, file uploads, external service integrations)
    Affected if The parser processes XML from user input, external systems, or untrusted network sources
  4. Check external entity configuration in parser setup
    Inspect the SAXParserFactory and DocumentBuilderFactory configuration in application code or check jboss-deployment-structure.xml for custom parser settings; look for features like 'external-general-entities' and 'external-parameter-entities' being set
    Affected if External entity processing is enabled (default) and the parser is not explicitly configured with setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true) or setAttribute for disabling entities
  5. Test for XXE vulnerability in affected endpoints
    Submit XML payloads with external entity references (e.g., <!DOCTYPE foo [<!ENTITY xxe SYSTEM 'file:///etc/passwd'>]>) to XML-processing endpoints and observe if entity expansion occurs or external resources are accessed
    Affected if The parser resolves external entities and returns expanded content

You are affected if running JBoss EAP exactly version 7.0 and any deployed application uses JAXP SAX or DOM parsers to process untrusted XML without explicitly disabling external entity processing.

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

Update JBoss EAP 7.0 to a patched version that addresses the XXE vulnerability in JAXP, or configure XML parsers to disable external entity processing.

Recommended fix Moderate confidence

JBoss EAP 7.1 or later

  1. 1. Back up your current JBoss EAP 7.0 installation and configuration files.
  2. 2. Download JBoss EAP 7.1 or later from the Red Hat Customer Portal.
  3. 3. Follow the JBoss EAP migration guide to upgrade from 7.0 to 7.1.
  4. 4. Test your applications to ensure compatibility with the new version.
  5. 5. Deploy the upgraded JBoss EAP to production.
Caveat Review the JBoss EAP 7.1 release notes for potential breaking changes, particularly around Java EE/Jakarta EE compliance and configuration differences from 7.0.

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

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7464 — 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-7464 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