# CVE-2015-7450: IBM WebSphere Application Server and Server Hypervisor Edition Code Injection.

> Remote attackers can execute arbitrary commands via crafted serialized Java objects in IBM products using Apache Commons Collections.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 10 Jan 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2016
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-8987-qgc7-79p9

## What is CVE-2015-7450?

CVE-2015-7450 is a critical unsafe deserialization vulnerability in Ibm Sterling B2b Integrator, published on 2 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Serialized-object interfaces in certain IBM analytics, business solutions, cognitive, IT infrastructure, and mobile and social products allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the InvokerTransformer class in the Apache Commons Collections library.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2015-7450?

It affects 7 products.


Products: Ibm Sterling B2b Integrator, Ibm Sterling Integrator, Ibm Tivoli Common Reporting, Ibm Watson Content Analytics, Ibm Watson Explorer Analytical Components, Ibm Watson Explorer Annotation Administration Console, Ibm Websphere Application Server.

## How do I fix CVE-2015-7450?

No fix has been published for CVE-2015-7450 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Jul 2022.

## Is CVE-2015-7450 being exploited?

Yes. Attackers have exploited CVE-2015-7450 in the wild since at least 10 Jan 2022.

Public exploit code:

- IBM WebSphere RCE Java Deserialization Vulnerability (metasploit)
- IBM WebSphere - RCE Java Deserialization (Metasploit) (exploitdb)
- IBM WebSphere Java Object Deserialization - Remote Code Execution (nuclei): http/cves/2015/CVE-2015-7450.yaml

## Other vulnerabilities in Ibm Sterling B2b Integrator

- [CVE-2024-31903](https://insights.sbomify.com/CVE-2024-31903/): IBM Sterling B2B Integrator Standard Edition code execution (high 8.8)
- [CVE-2019-4728](https://insights.sbomify.com/CVE-2019-4728/): Deserialization in Sterling B2B Integrator (high 8.8)
- [CVE-2020-4762](https://insights.sbomify.com/CVE-2020-4762/): Privilege escalation in Sterling B2B Integrator (high 8.8)
- [CVE-2017-1174](https://insights.sbomify.com/CVE-2017-1174/): SQL injection in Sterling B2B Integrator (high 8.8)
- [CVE-2017-1347](https://insights.sbomify.com/CVE-2017-1347/): SQL injection in Sterling B2B Integrator (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7450 and fix it if it is affected.

What it is: CVE-2015-7450 is a critical unsafe deserialization vulnerability in Ibm Sterling B2b Integrator, published on 2 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2015-7450 in the wild since at least 10 Jan 2022.

Affected product: Ibm Sterling B2b Integrator. 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-2015-7450/ (Markdown: https://insights.sbomify.com/CVE-2015-7450/index.md)
```

## Sources

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

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