# CVE-2012-0507: Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution

> Remote attackers can bypass Java sandbox restrictions or crash the JVM via a type confusion flaw in the Concurrency component.

- **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 3 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2012
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-43xj-964v-hcjf

## What is CVE-2012-0507?

CVE-2012-0507 is a critical vulnerability in Debian Debian Linux, published on 7 Jun 2012. 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 2 and earlier, 6 Update 30 and earlier, and 5.0 Update 33 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Concurrency.  NOTE: the previous information was obtained from the February 2012 Oracle CPU. Oracle has not commented on claims from a downstream vendor and third party researchers that this issue occurs because the AtomicReferenceArray class implementation does not ensure that the array is of the Object[] type, which allows attackers to cause a denial of service (JVM crash) or bypass Java sandbox restrictions.  NOTE: this issue was originally mapped to CVE-2011-3571, but that identifier was already assigned to a different issue.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2012-0507?

It affects 7 products.


Products: Debian Debian Linux, 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-2012-0507?

Apply the vendor's patch. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2012-0507 being exploited?

Yes. Attackers have exploited CVE-2012-0507 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Java AtomicReferenceArray Type Violation Vulnerability (metasploit)
- Java - AtomicReferenceArray Type Violation (Metasploit) (exploitdb)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0507 and fix it if it is affected.

What it is: CVE-2012-0507 is a critical vulnerability in Debian Debian Linux, published on 7 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2012-0507 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Affected product: Debian Debian Linux. 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-2012-0507/ (Markdown: https://insights.sbomify.com/CVE-2012-0507/index.md)
```

## Sources

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

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