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.
Publish Date : 2012-06-07 Last Update Date : 2014-02-06
(There is total information disclosure, resulting in all system files being revealed.)
(There is a total compromise of system integrity. There is a complete loss of system protection, resulting in the entire system being compromised.)
(There is a total shutdown of the affected resource. The attacker can render the resource completely unavailable.)
(Specialized access conditions or extenuating circumstances do not exist. Very little knowledge or skill is required to exploit. )
(Authentication is not required to exploit the vulnerability.)
Denial Of ServiceBypass a restriction or similar
||CWE id is not defined for this vulnerability
OVAL (Open Vulnerability and Assessment Language) definitions define exactly what should be done to verify
a vulnerability or a missing patch. Check out the OVAL definitions
if you want to learn what you should do to verify a vulnerability.