| ID | STATUS/COMMIT |
|---|---|
| CVE-2010-5321 | no patch available |
| CVE-2014-9410 | not affected |
| CVE-2015-0568 | not affected |
| CVE-2015-0569 | not affected |
| CVE-2015-0570 | not affected |
| CVE-2015-0571 | not affected |
| CVE-2015-0572 | not affected |
| CVE-2015-0573 | not affected |
| CVE-2015-1350 | not affected |
| CVE-2015-2877 | no patch available |
| CVE-2016-2059 | not affected |
| CVE-2016-2061 | not affected |
| CVE-2016-2062 | not affected |
| CVE-2016-2063 | not affected |
| CVE-2016-2064 | not affected |
| CVE-2016-2065 | not affected |
| CVE-2016-2066 | not affected |
| CVE-2016-2067 | not affected |
| CVE-2016-2068 | not affected |
| CVE-2016-5340 | not affected |
| CVE-2016-5342 | not affected |
| CVE-2016-5343 | not affected |
| CVE-2016-5344 | not affected |
| CVE-2016-5870 | not affected |
| CVE-2017-1000251 | not affected |
| CVE-2017-1000405 | not affected |
| CVE-2017-1000407 | not affected |
| CVE-2017-1000410 | 06e7e776ca4d36547e503279aeff996cbb292c16 |
| CVE-2017-12193 | not affected |
| CVE-2017-15102 | 2fae9e5a7babada041e2e161699ade2447a01989 |
| CVE-2017-15115 | df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 |
| CVE-2017-15116 | not affected |
| CVE-2017-15127 | not affected |
| CVE-2017-15129 | not affected |
| CVE-2017-15868 | 71bb99a02b32b4cc4265118e85f6035ca72923f0 |
| CVE-2017-16939(X) | I99ff2145d88095b5e7f555d56f41e0f06412b288 |
| CVE-2017-16994 | 373c4557d2aa362702c4c2d41288fb1e54990b7c |
| CVE-2017-17052 | 2b7e8665b4ff51c034c55df3cff76518d1a9ee3a |
| CVE-2017-17053 | not affected |
| CVE-2017-17805 | ecaaab5649781c5a0effdaf298a925063020500e |
| CVE-2017-17806 | af3ff8045bbf3e32f1a448542e73abb4c8ceb6f1 |
| CVE-2017-17807 | 4dca6ea1d9432052afb06baf2e3ae78188a4410b |
| CVE-2017-18075 | not affected |
| CVE-2017-18079 | 340d394a789518018f834ff70f7534fc463d3226 |
| CVE-2017-18174 | not affected |
| CVE-2017-18193 | not affected |
| CVE-2017-18203 | b9a41d21dceadf8104812626ef85dc56ee8a60ed |
| CVE-2017-18204 | 28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 |
| CVE-2017-18208 | 6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 |
| CVE-2017-18216 | 853bc26a7ea39e354b9f8889ae7ad1492ffa28d2 |
| CVE-2017-18218 | not affected |
| CVE-2017-18224 | not affected |
| CVE-2017-18241 | d4fdf8ba0e5808ba9ad6b44337783bd9935e0982 |
| CVE-2017-18255 | 1572e45a924f254d9570093abde46430c3172e3d |
| CVE-2017-18257 | b86e33075ed1909d8002745b56ecf73b833db143 |
| CVE-2017-18261 | not affected |
| CVE-2017-18270 | open |
| CVE-2017-5972 | not affected |
| CVE-2018-10021 | 318aaf34f1179b39fa9c30fa0f3288b645beee39 |
| CVE-2018-10074 | dd83c161fbcc5d8be637ab159c0de015cbff5ba4 |
| CVE-2018-10087 | not affected |
| CVE-2018-10124 | 4ea77014af0d6205b05503d1c7aac6eace11d473 |
| CVE-2018-10675 | 73223e4e2e3867ebf033a5a8eb2e5df0158ccc99 |
| CVE-2018-10940 | not affected |
| CVE-2018-11232 | not affected |
| CVE-2018-1130 | 67f93df79aeefc3add4e4b31a752600f834236e2 |
| CVE-2018-11508 | not affected |
| CVE-2018-6927 | fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a |
| CVE-2018-7480 | not affected |
| CVE-2018-8781 | 3b82a4db8eaccce735dffd50b4d4e1578099b8e8 |