dbcve.org
Websphere Mq JmsApplication · Ibm

CVE-2016-0360

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-15
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
IBM Websphere MQ JMS 7.0.1, 7.1, 7.5, 8.0, and 9.0 client provides classes that deserialize objects from untrusted sources which could allow a malicious user to execute arbitrary Java code by adding vulnerable classes to the classpath. IBM Reference #: 1983457.

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

IBM WebSphere MQ JMS client versions 7.0.1 through 9.0 contain classes that perform unsafe deserialization of objects from untrusted sources, allowing remote attackers to execute arbitrary Java code by supplying malicious serialized payloads.

MitigationApply IBM security patches for APAR IT14785; if unavailable, restrict network access to MQ endpoints and implement serialization white-listing via Java agent or custom object InputStream filters.

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
Websphere Mq JmsApplication
Affected:= 7.0.1= 7.1= 7.5= 8.0= 9.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 WebSphere MQ JMS client version
    Locate MQ JMS JAR files (typically com.ibm.mq*.jar in MQ_HOME/java/lib or application classpath) and check their version metadata, or run: java -cp <mq_jms_jar> com.ibm.mq.MQVersion or check the product.info file in the MQ installation directory
    Affected if The installed version matches 7.0.1, 7.1, 7.5, 8.0, or 9.0 (any version from 7.0.1 through 9.0)
  2. Verify JMS listener or client is configured to accept remote connections
    Examine MQ JMS connection factory and queue manager configurations in the application, JNDI bindings, or MQ explorer settings for remote client connection channels (SVRCONN) that accept connections from non-localhost sources
    Affected if The MQ JMS client is configured to receive or process JMS messages from network-accessible endpoints (non-loopback interfaces)
  3. Confirm lack of Java serialization filtering
    Inspect JVM startup arguments for -Djdk.serialFilter settings or custom ObjectInputStream filters configured in the application code for JMS message consumption
    Affected if No serialization whitelist or filter is configured in the JVM or application code, and the JMS client processes objects from remote sources

A user is affected if WebSphere MQ JMS client versions 7.0.1 through 9.0 are installed and the system processes JMS messages from untrusted or network-accessible sources without serialization filtering in place.

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 IBM security patches for APAR IT14785; if unavailable, restrict network access to MQ endpoints and implement serialization white-listing via Java agent or custom object InputStream filters.

Recommended fix Moderate confidence

IBM WebSphere MQ 9.0 or later (such as 9.0.0.1 or later)

  1. 1. Identify all systems running IBM WebSphere MQ JMS client versions 7.0.1, 7.1, 7.5, or 8.0
  2. 2. Review IBM's official fix documentation for CVE-2016-0360 on IBM Support website (fix list for WebSphere MQ)
  3. 3. Download and apply the appropriate interim fix (APAR IT14655) or upgrade to a fixed release
  4. 4. Test the fix in a non-production environment before deploying to production
  5. 5. Deploy the fix to production systems and verify the vulnerability is remediated
Caveat Upgrading major versions may require compatibility testing with existing applications; review IBM migration guides for WebSphere MQ

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

Fix this in Websphere Mq Jms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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