# CVE-2013-2465: Oracle Java SE Unspecified

> Remote attackers can bypass the Java sandbox via 2D image verification flaws, potentially executing arbitrary code or escalating privileges.

- **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 28 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jun 2013
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-498p-qg8p-wgxg

## What is CVE-2013-2465?

CVE-2013-2465 is a critical vulnerability in Oracle Jre, published on 18 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier, and OpenJDK 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.  NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue allows remote attackers to bypass the Java sandbox via vectors related to "Incorrect image channel verification" in 2D.

Weakness: CWE-693 (Protection Mechanism Failure)

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

It affects 6 products.


Products: Oracle Jre, Sun Jre, Suse Linux Enterprise Desktop, Suse Linux Enterprise Java, Suse Linux Enterprise Server, Suse Linux Enterprise Software Development Kit.

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

Apply the vendor's patch. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2013-2465 being exploited?

Yes. Attackers have exploited CVE-2013-2465 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Java storeImageArray() Invalid Array Indexing Vulnerability (metasploit)
- Java - 'storeImageArray()' Invalid Array Indexing (Metasploit) (exploitdb)

## Other vulnerabilities in Oracle Jre

- [CVE-2012-5076](https://insights.sbomify.com/CVE-2012-5076/): Oracle Java SE Sandbox Bypass (critical 9.8, exploited in the wild)
- [CVE-2013-0431](https://insights.sbomify.com/CVE-2013-0431/): Oracle JRE Sandbox Bypass (low 3.7, exploited in the wild)
- [CVE-2012-0497](https://insights.sbomify.com/CVE-2012-0497/): Other in n/a (critical 10.0)
- [CVE-2012-0498](https://insights.sbomify.com/CVE-2012-0498/): Other in n/a (critical 10.0)
- [CVE-2014-6485](https://insights.sbomify.com/CVE-2014-6485/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2465 is a critical vulnerability in Oracle Jre, published on 18 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2013-2465 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

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

## Sources

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

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