Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-17151
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10spc300
== 200r007c00
== 200r007c00spc100
== 200r007c00spc200
== 200r007c00spc600
== 200r007c00spc900
== 200r007c00spcb00
== 200r008c20
== 200r008c20spc700
== 200r008c20spc800
== 200r008c30
|
CVE-2017-17160
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
|
CVE-2017-17202
|
High
|
|
Feb 15, 2018
|
== 200r005c32
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17286
|
Medium
|
|
Feb 15, 2018
|
== 200r005c32
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17287
|
Medium
|
|
Feb 15, 2018
|
== 200r005c32
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17291
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17292
|
Low
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17293
|
Low
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17294
|
Low
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r008c20
== 200r008c30
|
CVE-2017-17295
|
Medium
|
|
Feb 15, 2018
|
== 200r006c10
== 200r007c00
== 200r008c20
== 200r008c30
|