This page was not yet optimized for use on mobile devices.
Qualcomm MDM9640 Firmware
Configuration details
| CPE title | Qualcomm MDM9640 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:mdm9640_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
495 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2014-10045 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10051 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10052 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10054 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10057 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10062 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2014-9998 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9119 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9122 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9123 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9124 | CRITICAL | 9.1 | 18.04.2018 | |
| CVE-2015-9126 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9135 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9136 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9137 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9138 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9139 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9140 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9143 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9144 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9145 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9148 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9191 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9197 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9198 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9199 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9201 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9208 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9209 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9213 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9220 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9224 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10410 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10412 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10414 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10415 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10416 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10417 | HIGH | 8.1 | 18.04.2018 | |
| CVE-2016-10419 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10421 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10422 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10427 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10429 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10433 | HIGH | 8.1 | 18.04.2018 | |
| CVE-2016-10435 | HIGH | 8.1 | 18.04.2018 | |
| CVE-2016-10436 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10437 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10438 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10442 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10443 | MEDIUM | 6.8 | 18.04.2018 | |
| CVE-2016-10448 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10449 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10450 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10451 | HIGH | 7.8 | 18.04.2018 | |
| CVE-2016-10455 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10456 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10459 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10464 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10466 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10479 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10481 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10482 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10484 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10485 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10486 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10487 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10490 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10491 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10492 | CRITICAL | 9.1 | 18.04.2018 | |
| CVE-2016-10493 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10494 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10497 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10499 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2017-18072 | HIGH | 7.5 | 11.04.2018 | |
| CVE-2017-18074 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2017-18124 | HIGH | 7.8 | 26.10.2018 | |
| CVE-2017-18126 | HIGH | 7.5 | 11.04.2018 | |
| CVE-2017-18136 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2017-18137 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2017-18139 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2017-18277 | MEDIUM | 5.5 | 23.10.2018 | |
| CVE-2017-18279 | HIGH | 7.8 | 06.05.2019 | |
| CVE-2017-18301 | MEDIUM | 5.5 | 20.09.2018 | |
| CVE-2017-18304 | HIGH | 7.8 | 23.10.2018 | |
| CVE-2017-18311 | HIGH | 7.8 | 26.10.2018 | |
| CVE-2017-18314 | CRITICAL | 9.8 | 20.09.2018 | |
| CVE-2017-18322 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18323 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18326 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18327 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18328 | HIGH | 7.8 | 03.01.2019 | |
| CVE-2017-18329 | HIGH | 7.8 | 03.01.2019 | |
| CVE-2017-18330 | HIGH | 7.8 | 03.01.2019 | |
| CVE-2017-18332 | MEDIUM | 5.5 | 18.01.2019 | |
| CVE-2017-8252 | MEDIUM | 5.5 | 14.06.2019 | |
| CVE-2017-9711 | HIGH | 7.8 | 22.11.2024 | |
| CVE-2018-11259 | HIGH | 7.7 | 06.07.2018 | |
| CVE-2018-11267 | HIGH | 7.8 | 20.09.2018 | |
| CVE-2018-11268 | HIGH | 7.8 | 20.09.2018 | |
| CVE-2018-11269 | HIGH | 7.8 | 20.09.2018 | |
| CVE-2018-11279 | HIGH | 8.8 | 18.01.2019 | |
| CVE-2018-11290 | HIGH | 7.5 | 20.09.2018 | |
| CVE-2018-11291 | HIGH | 7.5 | 20.09.2018 | |
| CVE-2018-11292 | HIGH | 7.8 | 20.09.2018 | |
| CVE-2018-11305 | HIGH | 7.8 | 26.10.2018 | |
| CVE-2018-11819 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-11820 | MEDIUM | 5.5 | 25.02.2019 | |
| CVE-2018-11838 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2018-11849 | HIGH | 7.8 | 26.10.2018 | |
| CVE-2018-11850 | HIGH | 7.8 | 26.10.2018 | |
| CVE-2018-11870 | HIGH | 7.8 | 29.10.2018 | |
| CVE-2018-11871 | HIGH | 7.8 | 29.10.2018 | |
| CVE-2018-11899 | HIGH | 7.8 | 11.02.2019 | |
| CVE-2018-11922 | MEDIUM | 5.5 | 26.11.2024 | |
| CVE-2018-11923 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11924 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11925 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11927 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11928 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11929 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-11930 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-11934 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-11936 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-11937 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-11939 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-11940 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-11942 | MEDIUM | 5.5 | 14.06.2019 | |
| CVE-2018-11945 | CRITICAL | 9.8 | 25.02.2019 | |
| CVE-2018-11947 | MEDIUM | 5.5 | 14.06.2019 | |
| CVE-2018-11949 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-11952 | HIGH | 7.8 | 26.11.2024 | |
| CVE-2018-11953 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-11955 | CRITICAL | 9.8 | 14.06.2019 | |
| CVE-2018-11966 | HIGH | 7.8 | 04.04.2019 | |
| CVE-2018-11967 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11968 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2018-11980 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2018-11982 | HIGH | 8.8 | 20.09.2018 | |
| CVE-2018-12005 | MEDIUM | 5.5 | 24.05.2019 | |
| CVE-2018-13886 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-13897 | HIGH | 7.5 | 25.07.2019 | |
| CVE-2018-13900 | HIGH | 7.8 | 25.02.2019 | |
| CVE-2018-13902 | HIGH | 7.5 | 14.06.2019 | |
| CVE-2018-13906 | CRITICAL | 9.1 | 14.06.2019 | |
| CVE-2018-13907 | MEDIUM | 5.3 | 14.06.2019 | |
| CVE-2018-13911 | CRITICAL | 9.8 | 14.06.2019 | |
| CVE-2018-13912 | MEDIUM | 5.5 | 25.02.2019 | |
| CVE-2018-13913 | HIGH | 7.8 | 25.02.2019 | |
| CVE-2018-13916 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2018-13924 | CRITICAL | 9.8 | 22.07.2019 | |
| CVE-2018-3583 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-3592 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2018-5837 | HIGH | 7.5 | 20.09.2018 | |
| CVE-2018-5839 | HIGH | 7.1 | 25.02.2019 | |
| CVE-2018-5852 | HIGH | 7.8 | 26.11.2024 | |
| CVE-2018-5871 | MEDIUM | 6.5 | 20.09.2018 | |
| CVE-2018-5877 | HIGH | 7.8 | 28.11.2018 | |
| CVE-2018-5883 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-5903 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-5911 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-5913 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-5915 | CRITICAL | 9.8 | 18.01.2019 | |
| CVE-2018-5916 | MEDIUM | 6.5 | 28.11.2018 | |
| CVE-2019-10480 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10483 | MEDIUM | 5.5 | 16.04.2020 | |
| CVE-2019-10485 | HIGH | 7.5 | 12.12.2019 | |
| CVE-2019-10486 | HIGH | 7.0 | 21.11.2019 | |
| CVE-2019-10487 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10491 | HIGH | 7.8 | 06.11.2019 | |
| CVE-2019-10493 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10494 | HIGH | 8.1 | 12.12.2019 | |
| CVE-2019-10497 | HIGH | 7.8 | 30.09.2019 | |
| CVE-2019-10498 | HIGH | 7.8 | 30.09.2019 | |
| CVE-2019-10500 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10503 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-10505 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-10507 | HIGH | 7.8 | 30.09.2019 | |
| CVE-2019-10508 | HIGH | 7.8 | 30.09.2019 | |
| CVE-2019-10511 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10512 | HIGH | 7.8 | 06.11.2019 | |
| CVE-2019-10515 | MEDIUM | 5.5 | 06.11.2019 | |
| CVE-2019-10516 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10518 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10524 | HIGH | 7.8 | 06.11.2019 | |
| CVE-2019-10525 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10526 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10527 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-10528 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-10529 | HIGH | 8.1 | 06.11.2019 | |
| CVE-2019-10530 | HIGH | 7.8 | 12.12.2019 | |
| CVE-2019-10535 | MEDIUM | 5.5 | 21.11.2019 | |
| CVE-2019-10536 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10539 | CRITICAL | 9.8 | 30.09.2019 | |
| CVE-2019-10542 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-10544 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10546 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10547 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-10550 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10551 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-10552 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10553 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10554 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10555 | HIGH | 7.8 | 12.12.2019 | |
| CVE-2019-10558 | HIGH | 7.8 | 21.01.2020 | |
| CVE-2019-10569 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-10572 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10574 | HIGH | 7.1 | 16.04.2020 | |
| CVE-2019-10577 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10584 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10585 | HIGH | 7.8 | 21.01.2020 | |
| CVE-2019-10586 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10587 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10588 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10593 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10594 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10595 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10603 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-10604 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-10607 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10609 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10610 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-10614 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10622 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-10625 | HIGH | 7.1 | 16.04.2020 | |
| CVE-2019-10626 | MEDIUM | 5.5 | 22.06.2020 | |
| CVE-2019-13994 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13995 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13998 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13999 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14000 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14011 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14018 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14019 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14020 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14021 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14022 | HIGH | 7.5 | 16.04.2020 | |
| CVE-2019-14026 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14028 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14031 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14032 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14033 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14036 | HIGH | 7.8 | 21.01.2020 | |
| CVE-2019-14037 | HIGH | 7.8 | 30.07.2020 | |
| CVE-2019-14038 | HIGH | 7.1 | 02.06.2020 | |
| CVE-2019-14039 | HIGH | 7.1 | 02.06.2020 | |
| CVE-2019-14040 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14041 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14049 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14052 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2019-14053 | HIGH | 7.1 | 02.06.2020 | |
| CVE-2019-14055 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14062 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14070 | HIGH | 7.0 | 16.04.2020 | |
| CVE-2019-14073 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14074 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14079 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14080 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14094 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-14095 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14097 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14098 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14101 | HIGH | 7.1 | 30.07.2020 | |
| CVE-2019-14110 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-14113 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-14114 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-14135 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-2239 | MEDIUM | 5.5 | 25.07.2019 | |
| CVE-2019-2240 | MEDIUM | 5.5 | 25.07.2019 | |
| CVE-2019-2242 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-2246 | HIGH | 7.8 | 06.11.2019 | |
| CVE-2019-2247 | HIGH | 7.8 | 24.05.2019 | |
| CVE-2019-2254 | CRITICAL | 9.8 | 25.07.2019 | |
| CVE-2019-2258 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2260 | HIGH | 7.0 | 22.07.2019 | |
| CVE-2019-2263 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2264 | HIGH | 7.8 | 22.07.2019 | |
| CVE-2019-2271 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2278 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2283 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2287 | CRITICAL | 9.8 | 22.07.2019 | |
| CVE-2019-2289 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2290 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2297 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-2298 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2299 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2302 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2303 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2305 | CRITICAL | 9.8 | 25.07.2019 | |
| CVE-2019-2307 | CRITICAL | 9.8 | 25.07.2019 | |
| CVE-2019-2309 | CRITICAL | 9.8 | 25.07.2019 | |
| CVE-2019-2310 | HIGH | 7.5 | 12.12.2019 | |
| CVE-2019-2311 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-2312 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2316 | HIGH | 8.8 | 25.07.2019 | |
| CVE-2019-2320 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-2323 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2324 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2325 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2326 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2328 | HIGH | 7.8 | 25.07.2019 | |
| CVE-2019-2330 | MEDIUM | 5.5 | 25.07.2019 | |
| CVE-2019-2331 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2332 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2335 | HIGH | 7.5 | 21.11.2019 | |
| CVE-2019-2337 | HIGH | 7.5 | 12.12.2019 | |
| CVE-2019-2341 | HIGH | 7.8 | 30.09.2019 | |
| CVE-2020-11115 | HIGH | 7.5 | 08.09.2020 | |
| CVE-2020-11116 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2020-11118 | HIGH | 7.5 | 08.09.2020 | |
| CVE-2020-11119 | HIGH | 7.5 | 21.01.2021 | |
| CVE-2020-11123 | MEDIUM | 5.5 | 12.11.2020 | |
| CVE-2020-11126 | CRITICAL | 9.1 | 09.06.2021 | |
| CVE-2020-11131 | HIGH | 7.8 | 12.11.2020 | |
| CVE-2020-11157 | HIGH | 7.5 | 02.11.2020 | |
| CVE-2020-11159 | CRITICAL | 9.1 | 09.06.2021 | |
| CVE-2020-11166 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11170 | CRITICAL | 9.8 | 22.02.2021 | |
| CVE-2020-11171 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11174 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-11177 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11188 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11189 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11190 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11191 | CRITICAL | 9.1 | 07.04.2021 | |
| CVE-2020-11192 | CRITICAL | 9.8 | 17.03.2021 | |
| CVE-2020-11195 | HIGH | 7.8 | 22.02.2021 | |
| CVE-2020-11199 | MEDIUM | 5.5 | 17.03.2021 | |
| CVE-2020-11204 | HIGH | 7.8 | 22.02.2021 | |
| CVE-2020-11221 | MEDIUM | 5.5 | 17.03.2021 | |
| CVE-2020-11226 | HIGH | 7.5 | 17.03.2021 | |
| CVE-2020-11227 | CRITICAL | 9.8 | 17.03.2021 | |
| CVE-2020-11233 | HIGH | 7.0 | 09.06.2021 | |
| CVE-2020-11234 | HIGH | 7.8 | 07.04.2021 | |
| CVE-2020-11235 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11241 | HIGH | 7.5 | 09.06.2021 | |
| CVE-2020-11251 | CRITICAL | 9.1 | 07.04.2021 | |
| CVE-2020-11255 | HIGH | 7.5 | 07.04.2021 | |
| CVE-2020-11267 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11269 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11275 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11276 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11279 | CRITICAL | 9.8 | 07.05.2021 | |
| CVE-2020-11285 | CRITICAL | 9.1 | 07.05.2021 | |
| CVE-2020-11289 | HIGH | 7.8 | 07.05.2021 | |
| CVE-2020-11292 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11293 | MEDIUM | 6.0 | 07.05.2021 | |
| CVE-2020-11296 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11301 | HIGH | 7.5 | 08.09.2021 | |
| CVE-2020-11303 | MEDIUM | 5.0 | 20.10.2021 | |
| CVE-2020-3614 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3620 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3621 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3622 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3624 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3630 | HIGH | 7.8 | 02.06.2020 | |
| CVE-2020-3634 | CRITICAL | 9.1 | 09.09.2020 | |
| CVE-2020-3639 | CRITICAL | 9.8 | 12.11.2020 | |
| CVE-2020-3651 | HIGH | 7.5 | 16.04.2020 | |
| CVE-2020-3657 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3665 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2020-3666 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3670 | CRITICAL | 9.1 | 02.11.2020 | |
| CVE-2020-3699 | CRITICAL | 9.8 | 30.07.2020 | |
| CVE-2020-3704 | HIGH | 7.5 | 02.11.2020 | |
| CVE-2021-1886 | HIGH | 7.8 | 13.07.2021 | |
| CVE-2021-1888 | HIGH | 7.8 | 13.07.2021 | |
| CVE-2021-1889 | HIGH | 7.8 | 13.07.2021 | |
| CVE-2021-1890 | HIGH | 7.8 | 13.07.2021 | |
| CVE-2021-1904 | MEDIUM | 5.5 | 08.09.2021 | |
| CVE-2021-1909 | HIGH | 7.8 | 09.09.2021 | |
| CVE-2021-1914 | HIGH | 7.5 | 08.09.2021 | |
| CVE-2021-1916 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1919 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1920 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1924 | MEDIUM | 5.5 | 12.11.2021 | |
| CVE-2021-1935 | MEDIUM | 5.5 | 09.09.2021 | |
| CVE-2021-1955 | HIGH | 7.5 | 13.07.2021 | |
| CVE-2021-1959 | HIGH | 7.2 | 20.10.2021 | |
| CVE-2021-1961 | MEDIUM | 6.7 | 09.09.2021 | |
| CVE-2021-1972 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1973 | HIGH | 7.2 | 12.11.2021 | |
| CVE-2021-1975 | HIGH | 10.0 | 12.11.2021 | |
| CVE-2021-1976 | HIGH | 10.0 | 17.09.2021 | |
| CVE-2021-30254 | HIGH | 7.2 | 12.11.2021 | |
| CVE-2021-30255 | HIGH | 7.2 | 12.11.2021 | |
| CVE-2021-30260 | HIGH | 7.8 | 17.09.2021 | |
| CVE-2021-30261 | HIGH | 7.8 | 17.09.2021 | |
| CVE-2021-30262 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30268 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30270 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30271 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30272 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30273 | HIGH | 7.5 | 03.01.2022 | |
| CVE-2021-30284 | CRITICAL | 9.1 | 12.11.2021 | |
| CVE-2021-30289 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30293 | HIGH | 7.5 | 03.01.2022 | |
| CVE-2021-30300 | HIGH | 7.5 | 13.01.2022 | |
| CVE-2021-30303 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30310 | MEDIUM | 5.0 | 20.10.2021 | |
| CVE-2021-30319 | HIGH | 7.8 | 13.01.2022 | |
| CVE-2021-30323 | HIGH | 7.8 | 11.02.2022 | |
| CVE-2021-30333 | HIGH | 7.8 | 01.04.2022 | |
| CVE-2021-30337 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30341 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2021-30342 | MEDIUM | 5.9 | 14.06.2022 | |
| CVE-2021-30344 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2021-30348 | MEDIUM | 6.5 | 03.01.2022 | |
| CVE-2021-35072 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2021-35083 | CRITICAL | 9.1 | 14.06.2022 | |
| CVE-2021-35098 | MEDIUM | 6.7 | 14.06.2022 | |
| CVE-2021-35116 | HIGH | 7.1 | 14.06.2022 | |
| CVE-2021-35135 | MEDIUM | 5.5 | 02.09.2022 | |
| CVE-2022-22058 | HIGH | 7.8 | 26.09.2022 | |
| CVE-2022-22062 | CRITICAL | 9.1 | 02.09.2022 | |
| CVE-2022-22063 | HIGH | 7.8 | 15.12.2022 | |
| CVE-2022-22064 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-22065 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-22074 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22076 | MEDIUM | 5.5 | 06.06.2023 | |
| CVE-2022-22080 | HIGH | 7.8 | 02.09.2022 | |
| CVE-2022-22105 | CRITICAL | 9.8 | 16.09.2022 | |
| CVE-2022-25651 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2022-25655 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25670 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25682 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25690 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25694 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25695 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25705 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25710 | HIGH | 7.5 | 15.11.2022 | |
| CVE-2022-25718 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25720 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25748 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25749 | HIGH | 7.5 | 19.10.2022 | |
| CVE-2022-33213 | HIGH | 8.8 | 10.03.2023 | |
| CVE-2022-33233 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33235 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-33238 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-33239 | HIGH | 7.5 | 15.11.2022 | |
| CVE-2022-33264 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-33271 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-33285 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33286 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33289 | MEDIUM | 6.8 | 13.04.2023 | |
| CVE-2022-33290 | HIGH | 7.5 | 09.01.2023 | |
| CVE-2022-33299 | HIGH | 7.5 | 09.01.2023 | |
| CVE-2022-33302 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-40510 | CRITICAL | 9.8 | 08.08.2023 | |
| CVE-2022-40512 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-40520 | HIGH | 7.8 | 09.01.2023 | |
| CVE-2022-40521 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2022-40531 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-40532 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2023-21628 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-22385 | CRITICAL | 9.8 | 03.10.2023 | |
| CVE-2023-22388 | CRITICAL | 9.8 | 07.11.2023 | |
| CVE-2023-24848 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-24849 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-28541 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-28546 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-28547 | HIGH | 7.8 | 01.04.2024 | |
| CVE-2023-28550 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-28551 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-28560 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-28563 | MEDIUM | 5.5 | 07.11.2023 | |
| CVE-2023-28564 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-28565 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-28586 | MEDIUM | 6.5 | 05.12.2023 | |
| CVE-2023-33018 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33023 | HIGH | 7.8 | 01.04.2024 | |
| CVE-2023-33030 | HIGH | 7.8 | 02.01.2024 | |
| CVE-2023-33031 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33033 | HIGH | 7.8 | 02.01.2024 | |
| CVE-2023-33059 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33066 | HIGH | 7.8 | 04.03.2024 | |
| CVE-2023-33080 | HIGH | 7.5 | 05.12.2023 | |
| CVE-2023-33120 | HIGH | 7.8 | 02.01.2024 | |
| CVE-2023-43511 | HIGH | 7.5 | 02.01.2024 | |
| CVE-2023-43551 | HIGH | 7.5 | 03.06.2024 | |
| CVE-2024-21461 | HIGH | 7.8 | 01.07.2024 | |
| CVE-2024-21468 | HIGH | 7.8 | 01.04.2024 | |
| CVE-2024-23353 | HIGH | 7.5 | 05.08.2024 | |
| CVE-2024-33051 | HIGH | 7.5 | 02.09.2024 | |
| CVE-2024-38422 | HIGH | 7.8 | 04.11.2024 | |
| CVE-2024-38426 | MEDIUM | 5.3 | 03.03.2025 | |
| CVE-2024-53027 | HIGH | 7.5 | 03.03.2025 | |
| CVE-2025-21428 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21429 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21430 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21482 | HIGH | 7.1 | 24.09.2025 | |
| CVE-2025-27053 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27074 | HIGH | 7.8 | 04.11.2025 | |
| CVE-2025-47318 | HIGH | 7.5 | 24.09.2025 | |
| CVE-2025-47320 | HIGH | 7.8 | 18.12.2025 | |
| CVE-2025-47383 | HIGH | 7.2 | 02.03.2026 |
Showing 5 out of 495.
Matched certificates
This CPE has no matched certificates.