# CVE-2013-0425: Security feature bypass in n/a

> Remote attackers can bypass Java sandbox restrictions via the logging API, potentially leading to privilege escalation and code execution.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 2 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-58g3-37cc-r74w

## What is CVE-2013-0425?

CVE-2013-0425 is a critical vulnerability in Oracle Jdk, published on 2 Feb 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, 6 through Update 38, 5.0 through Update 38, and 1.4.2_40 and earlier, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2013-0428 and CVE-2013-0426.  NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to incorrect "access control checks" in the logging API that allow remote attackers to bypass Java sandbox restrictions.

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

It affects 4 products.


Products: Oracle Jdk, Oracle Jre, Sun Jdk, Sun Jre.

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

Apply the vendor's patch.

## Is CVE-2013-0425 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0425 is a critical vulnerability in Oracle Jdk, published on 2 Feb 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-0425 in the wild and no public exploit code.

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

## Sources

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

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