Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-17294
|
Low
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
== 200r008c30
|
CVE-2017-17295
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
== 200r008c30
|
CVE-2017-17296
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
== 200r008c30
|
CVE-2017-17297
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
== 200r008c30
|
CVE-2017-17298
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
== 200r008c30
|
CVE-2017-17299
|
High
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
|
CVE-2017-17301
|
Critical
|
|
Feb 15, 2018
|
== 200r005c32
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
|
CVE-2014-4705
|
High
|
|
Jan 30, 2018
|
== 200r003c00spc100
== 200r003c00spc200
== 200r003c01spc100
== 200r003c01spc300
== 200r003c01spc900
== 200r005c00spc100
== 200r005c00spc200
|
CVE-2017-15317
|
High
|
|
Dec 22, 2017
|
== 200r006c10
== 200r007c00
== 200r007c01
== 200r008c20
== 200r008c30
|
CVE-2017-8147
|
High
|
|
Nov 22, 2017
|
== 200r005c20spc026t
|