# What is CVE-2012-0507?

> CVE-2012-0507 is a critical-severity flaw (CVSS 9.8) in JRE from Oracle, published on 7 June 2012. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 98%. If you run an affected version, patch it first.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2012-0507

## At a glance

- **Verdict:** Fix this now. Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
- **Precursor Intelligence risk score:** 90 out of 100 (Critical); action: Emergency patch. Kept up to date as the evidence changes.
- **Severity:** Critical (CVSS 9.8 out of 10)
- **Known to be exploited:** Yes, it is on the government list of flaws known to be exploited
- **Chance of use in the next 30 days:** 98% (latest exploit-likelihood forecast)
- **Published:** 7 June 2012
- **Record last updated:** 22 October 2025
- **Main product:** JRE from Oracle
- **Affected products:** 7

## What is CVE-2012-0507? In plain terms

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### The 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.

### What kind of flaw is it?

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

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Is CVE-2012-0507 being exploited? Yes

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 98%.

Exploit likelihood over the last 7 days: 98%, 98%, 98%, 98%, 98%, 98%, 98%.

### Timeline

- 7 June 2012: Published
- 22 October 2025: Record last updated

### How Precursor Intelligence ranks it

CVE-2012-0507 scores **90 out of 100 (Critical)**, with the action "Emergency patch".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2012-0507?

The published record lists 7 products.

- [JRE](https://www.precursorintelligence.com/product/oracle/jre) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): 1.6.0-update22, 1.6.0-update23, 1.6.0-update24, 1.6.0-update25, 1.6.0-update26, 1.6.0-update27, 1.6.0-update29, 1.6.0-update30, 1.7.0, 1.7.0-update1, 1.7.0-update2
- [JRE](https://www.precursorintelligence.com/product/sun/jre) by [Sun](https://www.precursorintelligence.com/vendors/sun) (Application): 1.5.0, 1.5.0-update1, 1.5.0-update2, 1.5.0-update3, 1.5.0-update4, 1.5.0-update5, 1.5.0-update6, 1.5.0-update7, 1.5.0-update8, 1.5.0-update9, 1.5.0-update10, 1.5.0-update11, 1.5.0-update12, 1.5.0-update13, 1.5.0-update14, 1.5.0-update15, 1.5.0-update16, 1.5.0-update17, 1.5.0-update18, 1.5.0-update19, 1.5.0-update20, 1.5.0-update21, 1.5.0-update22, 1.5.0-update23, 1.5.0-update24, 1.5.0-update25, 1.5.0-update26, 1.5.0-update27, 1.5.0-update28, 1.5.0-update29, 1.5.0-update31, 1.5.0-update33, 1.6.0, 1.6.0-update_1, 1.6.0-update_2, 1.6.0-update_3, 1.6.0-update_4, 1.6.0-update_5, 1.6.0-update_6, 1.6.0-update_7 and 12 more
- [Linux Enterprise Server](https://www.precursorintelligence.com/product/suse/linux_enterprise_server) by [Suse](https://www.precursorintelligence.com/vendors/suse) (Operating system): 10-sp4, 11-sp1, 11-sp2
- [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 6.0, 7.0
- [Linux Enterprise Java](https://www.precursorintelligence.com/product/suse/linux_enterprise_java) by [Suse](https://www.precursorintelligence.com/vendors/suse) (Operating system): 10-sp4, 11-sp1
- [Linux Enterprise Software Development Kit](https://www.precursorintelligence.com/product/suse/linux_enterprise_software_development_kit) by [Suse](https://www.precursorintelligence.com/vendors/suse) (Operating system): 11-sp1, 11-sp2
- [Linux Enterprise Desktop](https://www.precursorintelligence.com/product/suse/linux_enterprise_desktop) by [Suse](https://www.precursorintelligence.com/vendors/suse) (Operating system): 10-sp4

## How do I fix CVE-2012-0507?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Check it wasn’t used before you patched.** Because criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.

### References

- [blogs.technet.com](http://blogs.technet.com/b/mmpc/archive/2012/03/20/an-interesting-case-of-jre-sandbox-breach-cve-2012-0507.aspx) (Broken link, Third-party advisory)
- [krebsonsecurity.com](http://krebsonsecurity.com/2012/03/new-java-attack-rolled-into-exploit-packs/) (Third-party advisory)
- [lists.opensuse.org](http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00009.html) (Issue tracking, Third-party advisory)
- [lists.opensuse.org](http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00010.html) (Mailing list, Third-party advisory)
- [marc.info](http://marc.info/?l=bugtraq&m=133364885411663&w=2) (Third-party advisory)
- [marc.info](http://marc.info/?l=bugtraq&m=133365109612558&w=2) (Third-party advisory)

## Questions

### What is CVE-2012-0507?

CVE-2012-0507 is a critical-severity flaw in JRE from Oracle, published on 7 June 2012. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2012-0507?

It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2012-0507 is 90 out of 100, which is Critical. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.

### Is CVE-2012-0507 being exploited?

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 98%.

### Which versions does CVE-2012-0507 affect?

For JRE from Oracle: 1.6.0-update22, 1.6.0-update23, 1.6.0-update24, 1.6.0-update25, 1.6.0-update26, 1.6.0-update27 and 5 more. The record lists 7 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2012-0507?

Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.

## Does CVE-2012-0507 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact