dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2017-7504

CRITICAL · 9.8 CVSS v3.0 Published 2017-05-19
Fix available
A fix is available. Upgrade to after 4.0 or later.
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
HTTPServerILServlet.java in JMS over HTTP Invocation Layer of the JbossMQ implementation, which is enabled by default in Red Hat Jboss Application Server <= Jboss 4.X does not restrict the classes for which it performs deserialization, which allows remote attackers to execute arbitrary code via crafted serialized data.

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

This is an unsafe deserialization vulnerability in JBoss Application Server's JMS over HTTP Invocation Layer (JBossMQ). The HTTPServerILServlet component deserializes Java objects without restricting allowed classes, enabling remote attackers to execute arbitrary code by sending crafted serialized payloads.

MitigationUpgrade from vulnerable JBoss 4.X versions to supported versions, or disable the JMS over HTTP Invocation Layer if not required, combined with network access controls to limit exposure.

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:<= 4.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 installation and version
    Check for JBoss installation directories (typically under /opt/jboss, /usr/share/jboss, or similar paths) and locate the version file (often version.properties or jboss-version.txt in the installation root)
    Affected if JBoss Enterprise Application Platform version 4.0 or lower is found
  2. Locate the HTTPServerILServlet configuration
    Search for web.xml or jboss-web.xml configuration files in the deploy directory (commonly deploy/jbossweb-java2.sar/ or server/<profile>/deploy/jbossweb.sar/) and look for HTTPServerILServlet servlet definition and mapping
    Affected if The HTTPServerILServlet is defined and mapped to a URL pattern (typically /httphinv/* or similar JMS-related path)
  3. Verify JMS over HTTP is actively listening
    Check for running HTTP/HTTPS listeners on ports typically used by JBoss (often 8080, 8443, or custom ports) and examine active network listeners using netstat or ss commands, looking for JMS-related service bindings
    Affected if JBoss HTTP listener is active and JMS HTTP invocation layer is bound to a network interface
  4. Inspect JMS deployment configuration
    Examine files in the JBoss deploy directory for jms-related deployment descriptors (such as jms/hsqldb-jdbc2-service.xml, jms/jbossmq-httpil.sar, or similar JMS invocation layer deployments)
    Affected if JMS over HTTP Invocation Layer (jbossmq-httpil) is deployed and enabled

You are affected if you have JBoss EAP 4.0 or lower with the HTTPServerILServlet and JMS over HTTP Invocation Layer deployed and running.

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
Upgrade available Upgrade to a release after 4.0
Interim mitigation

Upgrade from vulnerable JBoss 4.X versions to supported versions, or disable the JMS over HTTP Invocation Layer if not required, combined with network access controls to limit exposure.

Recommended fix High confidence

JBoss EAP 6.x or 7.x (JBoss 4.x is end-of-life; migrate to modern supported EAP version)

  1. 1. Identify all systems running JBoss Application Server 4.x or JBoss EAP 4.x
  2. 2. Verify that the JMS over HTTP Invocation Layer (HTTPServerILServlet) is enabled on affected systems
  3. 3. Plan upgrade to a supported JBoss Enterprise Application Platform version (JBoss EAP 6.x or 7.x)
  4. 4. Before upgrade, back up all application data, configurations, and deployment artifacts
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Upgrade production systems to the new JBoss EAP version
  7. 7. Verify that applications function correctly post-upgrade
  8. 8. Confirm the vulnerability is no longer present by reviewing release notes of the target version
Caveat Major configuration changes between JBoss 4.x and EAP 6.x/7.x may require application code adjustments; review migration guide

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

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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