# CVE-2013-5456: Deserialization in n/a

> Remote attackers can bypass sandbox protections and execute arbitrary code via deserialization in IBM Java SDK.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qp4m-8934-3g25

## What is CVE-2013-5456?

CVE-2013-5456 is a critical unsafe deserialization vulnerability in n/a, published on 24 Nov 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The com.ibm.rmi.io.SunSerializableFactory class in IBM Java SDK 7.0.0 before SR6 allows remote attackers to bypass a sandbox protection mechanism and execute arbitrary code via vectors related to deserialization inside the AccessController doPrivileged block.

## Which versions are affected by CVE-2013-5456?

It affects 1 product.


Products: Ibm Java.

## How do I fix CVE-2013-5456?

Upgrade to a fixed version.

## Is CVE-2013-5456 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0485](https://insights.sbomify.com/CVE-2013-0485/): Other in n/a (critical 10.0)
- [CVE-2015-0192](https://insights.sbomify.com/CVE-2015-0192/): Privilege escalation in n/a (critical 9.8)
- [CVE-2013-5457](https://insights.sbomify.com/CVE-2013-5457/): Code injection in n/a (critical 9.3)
- [CVE-2013-5458](https://insights.sbomify.com/CVE-2013-5458/): Code injection in n/a (critical 9.3)
- [CVE-2013-3006](https://insights.sbomify.com/CVE-2013-3006/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5456 and fix it if it is affected.

What it is: CVE-2013-5456 is a critical unsafe deserialization vulnerability in n/a, published on 24 Nov 2013. 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-2013-5456 in the wild and no public exploit code.

Affected product: n/a. 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-2013-5456/ (Markdown: https://insights.sbomify.com/CVE-2013-5456/index.md)
```

## Sources

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

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