How severe is CVE-2012-0507?

CVE-2012-0507 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2012-0507?

Affected package information for CVE-2012-0507 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2012-0507?

No fixed version has been published for CVE-2012-0507 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2012-0507 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2012-0507, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2012-0507?

CVE-2012-0507 has an EPSS (Exploit Prediction Scoring System) score of 93.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2012-0507 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2012-0507 (Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-03-24. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2012-0507?

CVE-2012-0507 is classified as CWE-843 (CWE-843). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2012-0507?

CVE-2012-0507 affects debian debian linux (2 versions, e.g. 6.0, 7.0); oracle jre (2 versions, e.g. 1.6.0, 1.7.0); sun jre (2 versions, e.g. 1.5.0, 1.6.0); suse linux enterprise desktop (1 version, e.g. 10), and 3 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-0507 published, and has it been updated?

CVE-2012-0507 was published on June 7, 2012 and was last updated on April 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2012-0507: Debian Linux CWE-843 (Critical 9.8)

EPSS Exploitation Probability

via FIRST.org ↗

93.6%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

7 products · 74 configurations

OS

debian linuxdebian

2 versions

6.07.0

Application

jreoracle

2 versions

1.6.01.7.0

Application

jresun

2 versions

1.5.01.6.0

OS

linux enterprise desktopsuse

1 version

10

OS

linux enterprise javasuse

2 versions

1011

OS

linux enterprise serversuse

2 versions

1011

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2012-0507 in your stack?

O3 detects CVE-2012-0507 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works