# CVE-2013-0431: Oracle JRE Sandbox Bypass

> Attackers can bypass the Java security sandbox via JMX vectors, requiring user assistance, affecting Java SE and OpenJDK users.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 25 May 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2013
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-h3cw-j9j9-5pc4

## What is CVE-2013-0431?

CVE-2013-0431 is a low-severity vulnerability in Oracle Jre, published on 31 Jan 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 through Update 11, and OpenJDK 7, allows user-assisted remote attackers to bypass the Java security sandbox via unspecified vectors related to JMX, aka "Issue 52," a different vulnerability than CVE-2013-1490.

Weakness: CWE-693 (Protection Mechanism Failure)

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

It affects 2 products.


Products: Oracle Jre, Oracle Openjdk.

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

Upgrade to a fixed version. US federal agencies must fix it by 15 Jun 2022.

## Is CVE-2013-0431 being exploited?

Yes. Attackers have exploited CVE-2013-0431 in the wild since at least 25 May 2022, including in ransomware campaigns.

Public exploit code:

- Java Applet JMX Remote Code Execution (metasploit)
- Java Applet JMX - Remote Code Execution (Metasploit) (2) (exploitdb)

## Other vulnerabilities in Oracle Jre

- [CVE-2013-2465](https://insights.sbomify.com/CVE-2013-2465/): Oracle Java SE Unspecified (critical 9.8, exploited in the wild)
- [CVE-2012-5076](https://insights.sbomify.com/CVE-2012-5076/): Oracle Java SE Sandbox Bypass (critical 9.8, 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-0431 and fix it if it is affected.

What it is: CVE-2013-0431 is a low-severity vulnerability in Oracle Jre, published on 31 Jan 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-0431 in the wild since at least 25 May 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-0431/ (Markdown: https://insights.sbomify.com/CVE-2013-0431/index.md)
```

## Sources

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

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