Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2012-0507 | First vendor Publication | 2012-06-07 |
| Vendor | Cve | Last vendor Modification | 2013-02-14 |
Security-Database Scoring CVSS v2
| Cvss vector : (AV:N/AC:L/Au:N/C:C/I:C/A:C) | |||
|---|---|---|---|
| Cvss Base Score | 10 | Attack Range | Network |
| Cvss Impact Score | 10 | Attack Complexity | Low |
| Cvss Expoit Score | 10 | Authentification | None Required |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
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. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0507 |
CPE : Common Platform Enumeration
SAINT Exploits
| Description | Link |
|---|---|
| Java SE AtomicReferenceArray Unsafe Security Bypass | More info here |
ExploitDB Exploits
| id | Description |
|---|---|
| 2012-03-30 | Java AtomicReferenceArray Type Violation Vulnerability |
Metasploit Database
| id | Description |
|---|---|
| 2012-02-14 | Java AtomicReferenceArray Type Violation Vulnerability |
Internal Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2013-05-10 22:33:01 |
|
| 2013-05-01 17:22:41 |
|
| 2013-05-01 13:28:09 |
|
| 2013-05-01 09:22:50 |
|
| 2013-05-01 05:38:34 |
|
| 2013-02-15 13:20:26 |
|
| 2012-12-06 13:20:10 |
|

CVE-2012-0507
(Critical)







