| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2017-10334
|
Low
|
|
Oct 19, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-10336
|
Medium
|
|
Oct 19, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-10352
|
Critical
|
|
Oct 19, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
== 12.2.1.3.0
|
|
CVE-2017-10063
|
Low
|
|
Aug 8, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-10123
|
Low
|
|
Aug 8, 2017
|
== 12.1.3.0.0
|
|
CVE-2017-10137
|
Critical
|
|
Aug 8, 2017
|
== 12.1.3.0.0
== 10.3.6.0.0
|
|
CVE-2017-10147
|
High
|
|
Aug 8, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-10148
|
Medium
|
|
Aug 8, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-10178
|
Medium
|
|
Aug 8, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-3506
|
High
|
|
Apr 24, 2017
|
== 12.2.1.0.0
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|