Vulnerabilities > Use of Uninitialized Resource
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2020-12-10 | CVE-2020-26271 | Use of Uninitialized Resource vulnerability in Google Tensorflow In affected versions of TensorFlow under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. | 3.3 |
| 2020-11-28 | CVE-2020-29371 | Use of Uninitialized Resource vulnerability in Linux Kernel An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. | 3.3 |
| 2020-11-03 | CVE-2020-15989 | Use of Uninitialized Resource vulnerability in multiple products Uninitialized data in PDFium in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted PDF file. | 5.5 |
| 2020-10-14 | CVE-2020-0411 | Use of Uninitialized Resource vulnerability in Google Android 10.0/11.0 In ~AACExtractor() of AACExtractor.cpp, there is a possible out of bounds write due to uninitialized data. | 6.5 |
| 2020-10-02 | CVE-2020-17482 | Use of Uninitialized Resource vulnerability in Powerdns Authoritative An issue has been found in PowerDNS Authoritative Server before 4.3.1 where an authorized user with the ability to insert crafted records into a zone might be able to leak the content of uninitialized memory. | 4.3 |
| 2020-09-30 | CVE-2020-26148 | Use of Uninitialized Resource vulnerability in Md4C Project Md4C 0.4.5 md_push_block_bytes in md4c.c in md4c 0.4.5 allows attackers to trigger use of uninitialized memory, and cause a denial of service (e.g., assertion failure) via a malformed Markdown document. | 7.5 |
| 2020-09-25 | CVE-2020-15193 | Use of Uninitialized Resource vulnerability in multiple products In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of `dlpack.to_dlpack` can be made to use uninitialized memory resulting in further memory corruption. | 7.1 |
| 2020-09-18 | CVE-2020-0326 | Use of Uninitialized Resource vulnerability in Google Android 11.0 In NFC, there is a possible out of bounds write due to uninitialized data. | 6.7 |
| 2020-09-18 | CVE-2020-0300 | Use of Uninitialized Resource vulnerability in Google Android 11.0 In NFC, there is a possible out of bounds read due to uninitialized data. | 7.5 |
| 2020-09-18 | CVE-2020-0272 | Use of Uninitialized Resource vulnerability in Google Android 11.0 In libhwbinder, there is a possible information disclosure due to uninitialized data. | 4.4 |