Vulnerabilities > Divide By Zero
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2019-03-25 | CVE-2019-10019 | Divide By Zero vulnerability in Xpdfreader Xpdf 4.01.01 An issue was discovered in Xpdf 4.01.01. | 5.5 |
2019-03-25 | CVE-2019-10018 | Divide By Zero vulnerability in multiple products An issue was discovered in Xpdf 4.01.01. | 5.5 |
2019-03-21 | CVE-2018-19872 | Divide By Zero vulnerability in multiple products An issue was discovered in Qt 5.11. | 5.5 |
2019-01-31 | CVE-2017-18360 | Divide By Zero vulnerability in multiple products In change_port_settings in drivers/usb/serial/io_ti.c in the Linux kernel before 4.11.3, local users could cause a denial of service by division-by-zero in the serial device layer by trying to set very high baud rates. | 5.5 |
2019-01-29 | CVE-2019-7156 | Divide By Zero vulnerability in Libdoc Project Libdoc In libdoc through 2019-01-28, calcFileBlockOffset in ole.c allows division by zero. | 6.5 |
2018-12-28 | CVE-2018-20544 | Divide By Zero vulnerability in multiple products There is floating point exception at caca/dither.c (function caca_dither_bitmap) in libcaca 0.99.beta19. | 6.5 |
2018-12-06 | CVE-2018-16523 | Divide By Zero vulnerability in Amazon web Services Freertos and Freertos Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Connect middleware TCP/IP component allow division by zero in prvCheckOptions. | 7.4 |
2018-11-29 | CVE-2018-19628 | Divide By Zero vulnerability in multiple products In Wireshark 2.6.0 to 2.6.4, the ZigBee ZCL dissector could crash. | 7.5 |
2018-10-19 | CVE-2018-18521 | Divide By Zero vulnerability in multiple products Divide-by-zero vulnerabilities in the function arlib_add_symbols() in arlib.c in elfutils 0.174 allow remote attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by eu-ranlib, because a zero sh_entsize is mishandled. | 5.5 |
2018-10-09 | CVE-2018-18195 | Divide By Zero vulnerability in Linuxsampler Libgig 4.1.0 An issue was discovered in libgig 4.1.0. | 6.5 |