# CVE-2016-0360: Deserialization in WebSphere MQ

> Attackers can execute arbitrary Java code by exploiting unsafe deserialization in the IBM WebSphere MQ JMS client library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jx28-c3hv-9f4g

## What is CVE-2016-0360?

CVE-2016-0360 is a critical unsafe deserialization vulnerability in IBM Corporation WebSphere MQ, published on 15 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2016-0360?

It affects 1 product.


Products: Ibm Websphere Mq Jms.

## How do I fix CVE-2016-0360?

No fix has been published for CVE-2016-0360 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-0360 being exploited?

There is no known exploitation of CVE-2016-0360 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0360 and fix it if it is affected.

What it is: CVE-2016-0360 is a critical unsafe deserialization vulnerability in IBM Corporation WebSphere MQ, published on 15 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-0360 in the wild and no public exploit code.

Affected product: IBM Corporation WebSphere MQ. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-0360/ (Markdown: https://insights.sbomify.com/CVE-2016-0360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-0360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-0360
- OSV: https://osv.dev/vulnerability/CVE-2016-0360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-0360/
Summaries are generated and may contain mistakes; the official description above is the record.