CVE-2012-0507
CRITICALCISA KEVEPSS 100th pctlDescription
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.
How to fix
Actively exploited, no published fix found yet
CISA required action: Apply updates per vendor instructions.
Federal remediation due: 2022-03-24
Known ransomware campaign use
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 100% of all known CVEs.
Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution Vulnerability
An incorrect type vulnerability exists in the Concurrency component of Oracle's Java Runtime Environment allows an attacker to remotely execute arbitrary code.
Apply updates per vendor instructions.
Remediation due: 2022-03-24
Associated with ransomware campaigns
References
Related Vulnerabilities
Other CWE-843 (Type Confusion) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-8291 | High | 7.8 | 96% | KEV | Fix |
| CVE-2011-0611 | High | 8.8 | 94% | KEV | Fix |
| CVE-2019-0752 | High | 7.5 | 82% | KEV + Ransom | - |
| CVE-2017-0037 | High | 8.1 | 80% | KEV | - |
| CVE-2016-7201 | High | 8.8 | 80% | KEV | - |
| CVE-2020-6418 | High | 8.8 | 79% | KEV | Fix |
Common questions
How do I fix CVE-2012-0507?
No published fix for CVE-2012-0507 has been found yet. It is on the CISA Known Exploited Vulnerabilities list; federal agencies must remediate by 2022-03-24. Apply the vendor's mitigations per CISA's guidance.
Is CVE-2012-0507 being actively exploited?
Yes. CVE-2012-0507 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. CISA has also linked it to known ransomware campaigns. US federal agencies were required to remediate it by 2022-03-24. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2012-0507?
CVE-2012-0507 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2012-0507
Markdown
[](https://tridentstack.com/cve/CVE-2012-0507)HTML
<a href="https://tridentstack.com/cve/CVE-2012-0507"><img src="https://tridentstack.com/cve/badge/CVE-2012-0507.svg" alt="CVE-2012-0507"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-04-22.