| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2017-2692
|
High
|
|
Nov 22, 2017
|
<= crr-cl00c92b172
<= crr-l09c432b180
<= crr-tl00c01b172
<= crr-ul00c00b172
<= crr-ul20c432b171
|
|
CVE-2017-2693
|
High
|
|
Nov 22, 2017
|
<= crr-cl00c92b172
<= crr-l09c432b180
<= crr-tl00c01b172
<= crr-ul00c00b172
<= crr-ul20c432b171
|
|
CVE-2017-2699
|
High
|
|
Nov 22, 2017
|
< crr-l09c432b380
|
|
CVE-2015-8678
|
Medium
|
|
Mar 24, 2017
|
<= crr-cl00c92b153
<= crr-tl00c01b153sp01
<= crr-ul00c00b153
|
|
CVE-2016-8279
|
Medium
|
|
Sep 26, 2016
|
== crr-cl00
== crr-cl20
== crr-tl00
== crr-ul20
|
|
CVE-2015-8682
|
Medium
|
|
Apr 13, 2016
|
<= crr-cl00c92b153
<= crr-tl00c01b153sp01
<= crr-ul00c00b153
|
|
CVE-2016-1495
|
High
|
|
Apr 13, 2016
|
<= crr-cl00c92b153
<= crr-tl00c01b153sp01
<= crr-ul00c00b153
|
|
CVE-2015-8307
|
High
|
|
Apr 7, 2016
|
== crr-cl00
== crr-tl00
== crr-ul00
|
|
CVE-2015-8318
|
High
|
|
Apr 7, 2016
|
== crr-cl00
== crr-tl00
== crr-ul00
|
|
CVE-2015-8319
|
High
|
|
Apr 7, 2016
|
== crr-cl00
== crr-tl00
== crr-ul00
|