dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022. Known ransomware use
Debian LinuxOperating system · Debian

CVE-2012-0507

CRITICAL · 9.8 CVSS v3.1 Published 2012-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability exists in the AtomicReferenceArray class implementation within Java's concurrency utilities. The class fails to properly validate that the array is of Object[] type, allowing attackers to bypass Java sandbox restrictions or cause denial of service via JVM crashes. This enables remote code execution by circumventing Java's security model.

MitigationApply Java security updates released after the February 2012 Oracle Critical Patch Update. Upgrade to Java 7 Update 3 or later, Java 6 Update 31 or later, or Java 5.0 Update 34 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 6.0= 7.0
JreApplication
Affected:= 1.5.0= 1.6.0
JreApplication
Affected:= 1.6.0= 1.7.0
Linux Enterprise DesktopOperating system
Affected:= 10
Linux Enterprise JavaOperating system
Affected:= 10= 11
Linux Enterprise ServerOperating system
Affected:= 10= 11
Linux Enterprise Software Development KitOperating system
Affected:= 11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JRE/JDK version
    Run 'java -version' or 'java -fullversion' from command line to see the installed Java runtime version
    Affected if The version displayed is 1.7.0 (any update prior to 7u3), 1.6.0 (any update prior to 6u31), or 1.5.0 (any update prior to 5.0u34)
  2. Check Java vendor and build details
    Run 'java -version -verbose' or check the full version string which includes update number (for example: 1.6.0_30)
    Affected if The update number is 30 or lower for Java 6, 33 or lower for Java 5, or 2 or lower for Java 7
  3. Verify Java plugin browser configuration
    Check if Java plugin is enabled in browsers (Internet Explorer, Firefox, Chrome) as the vulnerability can be exploited via malicious applets loaded in browsers
    Affected if Java browser plugin is installed and enabled, and the underlying JRE is a vulnerable version

You are affected if the installed Java version is 1.7.0 update 2 or earlier, 1.6.0 update 30 or earlier, or 1.5.0 update 33 or earlier, and you run untrusted Java code or applets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Java security updates released after the February 2012 Oracle Critical Patch Update. Upgrade to Java 7 Update 3 or later, Java 6 Update 31 or later, or Java 5.0 Update 34 or later.

Recommended fix High confidence

Java SE 7 Update 3 or later, Java SE 6 Update 31 or later, or Java SE 5 Update 34 or later (or OpenJDK equivalents)

  1. 1. Identify the currently installed Java version by running 'java -version' or 'javac -version'
  2. 2. For Oracle Java SE: Download and install Java SE 7 Update 3 or later, Java SE 6 Update 31 or later, or Java SE 5 Update 34 or later from Oracle's official Java SE Downloads page (http://www.oracle.com/technetwork/java/javase/downloads/)
  3. 3. For Debian Linux systems: Run 'apt-get update && apt-get upgrade' to apply security updates, or specifically install openjdk-7-jdk (or later) via 'apt-get install openjdk-7-jdk'
  4. 4. For SUSE Linux Enterprise systems: Run 'zypper patch' or 'zypper update java-*' to apply available security patches
  5. 5. After installation, verify the fix by running 'java -version' and confirming the version is at least 1.5.0_34, 1.6.0_31, 1.7.0_03, or later
  6. 6. If using Java in browsers (Java Plug-in), ensure browsers are restarted and consider disabling the Java Plug-in until patches are applied if running vulnerable versions
  7. 7. Re-scan or re-assess systems to confirm remediation
Caveat Major version upgrades may require recompilation or testing of Java applications; Java 5/6 are end-of-life and should be migrated to Java 7 or later if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0507 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data