Vulnerabilities > DEPRECATED: Use of Uninitialized Resource
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2019-09-27 | CVE-2019-9359 | DEPRECATED: Use of Uninitialized Resource vulnerability in Google Android 10.0 In libavc there is a possible information disclosure due to uninitialized data. | 4.3 |
2019-09-27 | CVE-2019-9252 | DEPRECATED: Use of Uninitialized Resource vulnerability in Google Android 10.0 In libavc there is a possible out of bounds read due to uninitialized data. | 4.3 |
2019-09-27 | CVE-2019-2172 | DEPRECATED: Use of Uninitialized Resource vulnerability in Google Android 10.0 In libxaac there is a possible information disclosure due to uninitialized data. | 4.3 |
2019-09-27 | CVE-2019-2140 | DEPRECATED: Use of Uninitialized Resource vulnerability in Google Android 10.0 In libxaac, there is a possible information disclosure due to uninitialized data. | 4.3 |
2018-06-11 | CVE-2017-5405 | DEPRECATED: Use of Uninitialized Resource vulnerability in multiple products Certain response codes in FTP connections can result in the use of uninitialized values for ports in FTP operations. | 5.0 |
2017-05-10 | CVE-2017-8891 | DEPRECATED: Use of Uninitialized Resource vulnerability in Dropbox Lepton 1.2.1 Dropbox Lepton 1.2.1 allows DoS (SEGV and application crash) via a malformed lepton file because the code does not ensure setup of a correct number of threads. | 4.3 |