WaratekVRT Sign in

Java SE CPU Feb 2012

Released February 2012 · Oracle's advisory ↗ · ← Critical Patch Update, January 2012 · Critical Patch Update, April 2012 →

14 CVEs in this release, one square each

No exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedOutside Waratek scope, exploitedOutside Waratek scopeOutside Waratek scopeOutside Waratek scopeOutside Waratek scopeOutside Waratek scopeOutside Waratek scopeOutside Waratek scopeOutside Waratek scope
Share this chart Java SE CPU Feb 2012, one square per CVE: 5 Java CVEs, 1 exploited, 9 other CVEs in this release.

Download the image

By status

5No exploit published9Outside Waratek scope 1Exploited, marked by the ring

No exploit published. For 5 of them, Oracle's security advisory is the source of public detail.

Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Protection: None✕
Overview 1 match · 0 in Waratek scope · 0 protected
1match 0in Waratek scope0.0% 0protected0.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% Outside Waratek scope 1 100.0% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 1 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 1 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 100.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 1 / month
Outside Waratek scope: 1 Critical: 1 not blocked: 1 Exploited: 1
Jun 121 Outside Waratek scope1 Critical1 not blocked1 Exploited1
Jun 12
1 match Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2012-0507 Critical 2012-06-07 Outside Waratek scope Exploited 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.