dbcve.org
Data GridApplication · Redhat

CVE-2015-7501

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-09
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
High EPSS 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
Red Hat JBoss A-MQ 6.x; BPM Suite (BPMS) 6.x; BRMS 6.x and 5.x; Data Grid (JDG) 6.x; Data Virtualization (JDV) 6.x and 5.x; Enterprise Application Platform 6.x, 5.x, and 4.3.x; Fuse 6.x; Fuse Service Works (FSW) 6.x; Operations Network (JBoss ON) 3.x; Portal 6.x; SOA Platform (SOA-P) 5.x; Web Server (JWS) 3.x; Red Hat OpenShift/xPAAS 3.x; and Red Hat Subscription Asset Manager 1.3 allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.

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 a critical Java deserialization vulnerability in the Apache Commons Collections (ACC) library that affects multiple JBoss products. Attackers can craft malicious serialized Java objects that, when deserialized by vulnerable applications, trigger arbitrary method invocation leading to remote code execution. The flaw stems from the library's handling of the InvokerTransformer class during object deserialization, allowing attacker-controlled method calls.

MitigationApply vendor-supplied patches or upgrade to non-vulnerable product versions. If patches are unavailable, implement network-level controls to restrict deserialization endpoints or deploy Java deserialization filters to block untrusted object streams.

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
Data GridApplication
Affected:= 6.0.0
Jboss A MqApplication
Affected:= 6.0.0
Jboss Bpm SuiteApplication
Affected:= 6.0.0
Jboss Data VirtualizationApplication
Affected:= 5.0.0= 6.0.0
Jboss Enterprise Application PlatformApplication
Affected:= 4.3.0= 5.0.0= 6.0.0
Jboss Enterprise Brms PlatformApplication
Affected:= 5.0.0= 6.0.0
Jboss Enterprise Soa PlatformApplication
Affected:= 5.0.0
Jboss Enterprise Web ServerApplication
Affected:= 3.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 installed JBoss product and version
    Check the product's version file or startup logs. For JBoss EAP, examine the $JBOSS_HOME/bin/version.sh output or the MANIFEST.MF file in the jboss-modules.jar. For other products, locate the version metadata in the installation directory or startup banner.
    Affected if The installed product matches any of these: Redhat Data Grid 6.0.0, Redhat Jboss A Mq 6.0.0, Redhat Jboss Bpm Suite 6.0.0, Redhat Jboss Data Virtualization 5.0.0 or 6.0.0, Redhat Jboss Enterprise Application Platform 4.3.0, 5.0.0, or 6.0.0, Redhat Jboss Enterprise Brms Platform 5.0.0 or 6.0.0, Redha
  2. Locate Apache Commons Collections library in the installation
    Search the installation directory for commons-collections*.jar files. Common locations include $JBOSS_HOME/modules/org/apache/commons/collections/ or the lib directory of the deployed application.
    Affected if A commons-collections JAR file exists in the JBoss installation or in the application's WEB-INF/lib directory.
  3. Check Commons Collections version
    Examine the JAR file name or inspect the MANIFEST.MF file inside the commons-collections JAR to determine the exact version number.
    Affected if The Commons Collections library version is 3.2.1 or earlier, or the version cannot be determined from the JAR metadata.
  4. Verify InvokerTransformer class is present
    Use a JAR inspection tool (such as jar tf or a ZIP viewer) to list the classes in the commons-collections JAR and confirm that org.apache.commons.collections.functors.InvokerTransformer exists.
    Affected if The InvokerTransformer class is present in the Commons Collections library included with the product.
  5. Identify Java deserialization endpoints
    Review application configuration files (such as web.xml, jboss-web.xml, or custom serde-config.xml) and application code to locate endpoints or services that accept Java serialized object streams. Check for usage of ObjectInputStream or similar deserialization mechanisms.
    Affected if The application or server exposes any network-accessible interface that performs Java object deserialization without strict filtering.

You are affected if you are running any of the listed JBoss product versions AND the vulnerable Apache Commons Collections library with the InvokerTransformer class is present in the classpath AND your environment accepts Java deserialized object streams on any exposed endpoint.

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

Apply vendor-supplied patches or upgrade to non-vulnerable product versions. If patches are unavailable, implement network-level controls to restrict deserialization endpoints or deploy Java deserialization filters to block untrusted object streams.

Recommended fix Moderate confidence

Apply latest Red Hat security updates for each respective product via RHN/RHSM; for JBoss EAP 6.x this means updating to the latest EAP 6.4.x with all errata applied

  1. Subscribe to Red Hat Network (RHN) or Red Hat Subscription Management for the affected systems
  2. Run 'yum update' or 'yum list updates' to check for available security updates
  3. Apply the Red Hat Security Advisory (RHSA) patches for this CVE. For JBoss EAP, this is typically addressed in the latest JBoss EAP 6.4.x updates and 5.x patch bundles
  4. For JBoss A-MQ: apply the latest A-MQ 6.x security updates from Red Hat
  5. For JBoss Data Grid: apply the latest JDG 6.x updates
  6. For JBoss BPM Suite/BRMS: apply the latest BPMS/BRMS 6.x and 5.x updates
  7. For JBoss Data Virtualization: apply the latest JDV 6.x and 5.x updates
  8. For JBoss Enterprise SOA Platform: apply the latest SOA-P 5.x updates
Caveat Patching may require service restart; ensure change management procedures are followed for production systems

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

Fix this in Data Grid 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 help mitigating

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-2015-7501 — 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-2015-7501 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