Total
354 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-29659 | 2 Fedoraproject, Struktur | 2 Fedora, Libheif | 2024-08-02 | 6.5 Medium |
| A Segmentation fault caused by a floating point exception exists in libheif 1.15.1 using crafted heif images via the heif::Fraction::round() function in box.cc, which causes a denial of service. | ||||
| CVE-2023-25511 | 3 Linux, Microsoft, Nvidia | 3 Linux Kernel, Windows, Cuda Toolkit | 2024-08-02 | 3.3 Low |
| NVIDIA CUDA Toolkit for Linux and Windows contains a vulnerability in cuobjdump, where a division-by-zero error may enable a user to cause a crash, which may lead to a limited denial of service. | ||||
| CVE-2023-23109 | 1 Crasm Project | 1 Crasm | 2024-08-02 | 7.5 High |
| In crasm 1.8-3, invalid input validation, specific files passed to the command line application, can lead to a divide by zero fault in the function opdiv. | ||||
| CVE-2023-21789 | 1 Microsoft | 1 3d Builder | 2024-08-02 | 7.8 High |
| 3D Builder Remote Code Execution Vulnerability | ||||
| CVE-2023-3044 | 1 Xpdfreader | 1 Xpdf | 2024-08-02 | 3.3 Low |
| An excessively large PDF page size (found in fuzz testing, unlikely in normal PDF files) can result in a divide-by-zero in Xpdf's text extraction code. This is related to CVE-2022-30524, but the problem here is caused by a very large page size, rather than by a very large character coordinate. | ||||
| CVE-2023-2839 | 1 Gpac | 1 Gpac | 2024-08-02 | 7.5 High |
| Divide By Zero in GitHub repository gpac/gpac prior to 2.2.2. | ||||
| CVE-2023-2662 | 1 Xpdfreader | 1 Xpdf | 2024-08-02 | 2.9 Low |
| In Xpdf 4.04 (and earlier), a bad color space object in the input PDF file can cause a divide-by-zero. | ||||
| CVE-2023-1127 | 2 Fedoraproject, Vim | 2 Fedora, Vim | 2024-08-02 | 7.8 High |
| Divide By Zero in GitHub repository vim/vim prior to 9.0.1367. | ||||
| CVE-2023-0615 | 1 Linux | 1 Linux Kernel | 2024-08-02 | 5.5 Medium |
| A memory leak flaw and potential divide by zero and Integer overflow was found in the Linux kernel V4L2 and vivid test code functionality. This issue occurs when a user triggers ioctls, such as VIDIOC_S_DV_TIMINGS ioctl. This could allow a local user to crash the system if vivid test code enabled. | ||||
| CVE-2023-0512 | 1 Vim | 1 Vim | 2024-08-02 | 7.8 High |
| Divide By Zero in GitHub repository vim/vim prior to 9.0.1247. | ||||
| CVE-2024-21438 | 1 Microsoft | 12 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 9 more | 2024-08-01 | 7.5 High |
| Microsoft AllJoyn API Denial of Service Vulnerability | ||||
| CVE-2021-20242 | 2023-11-07 | 0.0 Low | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2021-20176. Reason: This candidate is a reservation duplicate of CVE-2021-20176. Notes: All CVE users should reference CVE-2021-20176 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | ||||
| CVE-2021-20189 | 2023-11-07 | 0.0 Low | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none | ||||
| CVE-2018-15672 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-11207. Reason: This candidate is a reservation duplicate of CVE-2018-11207. Notes: All CVE users should reference CVE-2018-11207 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage | ||||