Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2012-5606
|
Low
|
|
Dec 18, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.8
== 4.0.1
== 4.0.6
== 4.0.5
== 4.5.0
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.7
== 4.0.4
== 3.0.1
|
CVE-2012-5607
|
Medium
|
|
Dec 18, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.8
== 4.0.1
== 4.0.6
== 4.0.5
== 4.5.0
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.7
== 4.0.4
== 3.0.1
|
CVE-2012-5609
|
Medium
|
|
Dec 18, 2012
|
== 4.0.3
<= 4.5.1
== 4.0.0
== 3.0.3
== 4.0.8
== 4.0.1
== 4.0.6
== 4.0.5
== 4.5.0
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.9
== 4.0.7
== 4.0.4
== 3.0.1
|
CVE-2012-5610
|
Medium
|
|
Dec 18, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.8
== 4.0.1
== 4.0.6
== 4.0.5
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.7
== 4.0.4
== 3.0.1
|
CVE-2012-4389
|
Medium
|
|
Sep 6, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.6
== 4.0.1
== 4.0.5
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.4
== 3.0.1
|
CVE-2012-4390
|
Low
|
|
Sep 6, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.6
== 4.0.1
== 4.0.5
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.4
== 3.0.1
|
CVE-2012-4391
|
Medium
|
|
Sep 6, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.6
== 4.0.1
== 4.0.5
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.4
== 3.0.1
|
CVE-2012-4393
|
Medium
|
|
Sep 6, 2012
|
== 4.0.3
== 4.0.0
== 3.0.3
<= 4.0.5
== 4.0.1
== 4.0.2
== 3.0.0
== 3.0.2
== 4.0.4
== 3.0.1
|
CVE-2012-4394
|
Low
|
|
Sep 6, 2012
|
== 4.0.3
== 4.0.0
<= 4.0.4
== 3.0.3
== 4.0.1
== 4.0.2
== 3.0.0
== 3.0.2
== 3.0.1
|
CVE-2012-4395
|
Low
|
|
Sep 6, 2012
|
== 4.0.0
<= 4.0.2
== 4.0.1
== 3.0.0
== 3.0.2
== 3.0.1
|