Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2012-6591
|
High
|
|
Aug 31, 2013
|
<= 3.1.9
== 4.0.2
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.4
|
CVE-2012-6592
|
High
|
|
Aug 31, 2013
|
<= 3.1.9
== 4.0.2
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.4
|
CVE-2012-6593
|
High
|
|
Aug 31, 2013
|
<= 3.1.9
== 4.0.2
== 4.0.3
== 4.0.0
== 4.0.1
|
CVE-2012-6594
|
High
|
|
Aug 31, 2013
|
== 4.1.0
== 3.1.9
== 4.0.2
<= 3.1.10
== 4.0.5
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.4
== 4.0.6
|
CVE-2012-6595
|
High
|
|
Aug 31, 2013
|
== 4.1.0
== 4.0.2
== 4.0.5
== 4.1.1
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.8
== 4.0.4
== 4.0.6
|
CVE-2012-6596
|
Medium
|
|
Aug 31, 2013
|
== 4.1.0
== 4.1.2
== 4.0.2
== 4.0.5
== 4.1.1
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.8
== 4.0.4
== 4.0.6
|
CVE-2012-6597
|
Medium
|
|
Aug 31, 2013
|
== 3.1.9
== 4.0.2
<= 3.1.10
== 4.0.5
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.8
== 4.0.4
== 4.0.6
|
CVE-2012-6598
|
High
|
|
Aug 31, 2013
|
== 4.0.2
== 4.0.5
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.4
== 4.0.6
|
CVE-2012-6599
|
High
|
|
Aug 31, 2013
|
== 4.1.0
== 4.0.2
== 4.0.5
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.4
== 4.0.6
|
CVE-2012-6600
|
High
|
|
Aug 31, 2013
|
== 4.1.0
== 4.0.2
== 4.0.5
== 4.1.1
== 4.0.3
== 4.0.0
== 4.0.1
== 4.0.7
== 4.0.8
== 4.0.4
== 4.0.6
|