Total
544 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2019-9411 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112204845 | ||||
| CVE-2019-9410 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112204443 | ||||
| CVE-2019-9409 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libhevc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112272091 | ||||
| CVE-2019-9408 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112380157 | ||||
| CVE-2019-9406 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libhevc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112552517 | ||||
| CVE-2019-9391 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libxaac, there is a possible out of bounds read due to uninitialized data. This could lead to information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-111050781 | ||||
| CVE-2019-9369 | 1 Google | 1 Android | 2024-11-21 | 5.5 Medium |
| In Bluetooth, there is a use of uninitialized variable. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-79995407 | ||||
| CVE-2019-9361 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-111762807 | ||||
| CVE-2019-9359 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-111407302 | ||||
| CVE-2019-9338 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-111762686 | ||||
| CVE-2019-9337 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112204376 | ||||
| CVE-2019-9336 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112326322 | ||||
| CVE-2019-9335 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112328051 | ||||
| CVE-2019-9334 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libhevc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112859934 | ||||
| CVE-2019-9329 | 1 Google | 1 Android | 2024-11-21 | 7.5 High |
| In Bluetooth, there is a possible out of bounds read due to uninitialized data. This could lead to remote information disclosure, with no additional privileges required. User interaction is not needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-112917952 | ||||
| CVE-2019-9322 | 1 Google | 1 Android | 2024-11-21 | 6.5 Medium |
| In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-111128067 | ||||
| CVE-2019-7321 | 1 Artifex | 1 Mupdf | 2024-11-21 | N/A |
| Usage of an uninitialized variable in the function fz_load_jpeg in Artifex MuPDF 1.14 can result in a heap overflow vulnerability that allows an attacker to execute arbitrary code. | ||||
| CVE-2019-6976 | 1 Libvips | 1 Libvips | 2024-11-21 | N/A |
| libvips before 8.7.4 generates output images from uninitialized memory locations when processing corrupted input image data because iofuncs/memory.c does not zero out allocated memory. This can result in leaking raw process memory contents through the output image. | ||||
| CVE-2019-5818 | 5 Debian, Fedoraproject, Google and 2 more | 6 Debian Linux, Fedora, Chrome and 3 more | 2024-11-21 | 6.5 Medium |
| Uninitialized data in media in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted video file. | ||||
| CVE-2019-5067 | 1 Aspose | 1 Aspose.pdf For C\+\+ | 2024-11-21 | 9.8 Critical |
| An uninitialized memory access vulnerability exists in the way Aspose.PDF 19.2 for C++ handles invalid parent object pointers. A specially crafted PDF can cause a read and write from uninitialized memory, resulting in memory corruption and possibly arbitrary code execution. To trigger this vulnerability, a specifically crafted PDF document needs to be processed by the target application. | ||||