Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2012-3388
|
Low
|
|
Jul 23, 2012
|
== 2.2.2
== 2.2.1
== 2.2.3
== 2.2.0
== 2.3.0
|
CVE-2012-3389
|
Low
|
|
Jul 23, 2012
|
== 2.2.2
== 2.2.1
== 2.2.3
== 2.2.0
== 2.3.0
|
CVE-2012-3390
|
Low
|
|
Jul 23, 2012
|
== 2.2.2
== 2.1.2
== 2.1.1
== 2.1.5
== 2.1.6
== 2.1.3
== 2.2.1
== 2.2.3
== 2.1.4
== 2.1.0
== 2.2.0
|
CVE-2012-3391
|
Low
|
|
Jul 23, 2012
|
== 2.2.2
== 2.1.2
== 2.1.1
== 2.1.5
== 2.1.6
== 2.1.3
== 2.2.1
== 2.2.3
== 2.1.4
== 2.1.0
== 2.2.0
|
CVE-2012-3392
|
Medium
|
|
Jul 23, 2012
|
== 2.2.2
== 2.1.2
== 2.1.1
== 2.1.5
== 2.1.6
== 2.1.3
== 2.2.1
== 2.2.3
== 2.1.4
== 2.1.0
== 2.2.0
|
CVE-2012-3393
|
Low
|
|
Jul 23, 2012
|
== 2.2.2
== 2.1.2
== 2.1.1
== 2.1.5
== 2.1.6
== 2.1.3
== 2.2.1
== 2.2.3
== 2.1.4
== 2.1.0
== 2.2.0
|
CVE-2012-3394
|
Medium
|
|
Jul 23, 2012
|
== 2.2.2
== 2.1.2
== 2.1.1
== 2.1.5
== 2.1.6
== 2.1.3
== 2.2.1
== 2.2.3
== 2.1.4
== 2.1.0
== 2.2.0
== 2.3.0
|
CVE-2012-3395
|
Medium
|
|
Jul 23, 2012
|
== 2.0.2
== 2.2.2
== 2.0.1
== 2.1.2
== 2.0.4
== 2.0.3
== 2.1.1
== 2.1.5
== 2.1.6
== 2.0.6
== 2.0.5
== 2.1.3
== 2.0.9
== 2.2.1
== 2.2.3
== 2.0.8
== 2.0.7
== 2.1.4
== 2.0.0
== 2.1.0
== 2.2.0
|
CVE-2012-3396
|
Low
|
|
Jul 23, 2012
|
== 2.0.2
== 2.2.2
== 2.0.1
== 2.1.2
== 2.0.4
== 2.0.3
== 2.1.1
== 2.1.5
== 2.1.6
== 2.0.6
== 2.0.5
== 2.1.3
== 2.0.9
== 2.2.1
== 2.2.3
== 2.0.8
== 2.0.7
== 2.1.4
== 2.0.0
== 2.1.0
== 2.2.0
== 2.3.0
|
CVE-2012-3397
|
Low
|
|
Jul 23, 2012
|
== 2.0.2
== 2.2.2
== 2.0.1
== 2.1.2
== 2.0.4
== 2.0.3
== 2.1.1
== 2.1.5
== 2.1.6
== 2.0.6
== 2.0.5
== 2.1.3
== 2.0.9
== 2.2.1
== 2.2.3
== 2.0.8
== 2.0.7
== 2.1.4
== 2.0.0
== 2.1.0
== 2.2.0
== 2.3.0
|