Vulnerabilities > Google > Android > 10.0
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2019-09-27 | CVE-2019-9299 | Integer Overflow or Wraparound vulnerability in Google Android 10.0 In libAACdec, there is a possible out of bounds write due to an integer overflow. | 6.8 |
2019-09-27 | CVE-2019-9298 | Integer Overflow or Wraparound vulnerability in Google Android 10.0 In libAACdec, there is a possible out of bounds write due to an integer overflow. | 6.8 |
2019-09-27 | CVE-2019-9297 | Integer Overflow or Wraparound vulnerability in Google Android 10.0 In libAACdec, there is a possible out of bounds write due to an integer overflow. | 6.8 |
2019-09-27 | CVE-2019-9296 | Out-of-bounds Read vulnerability in Google Android 10.0 In NFC, there is a possible out of bounds read due to a missing bounds check. | 1.9 |
2019-09-27 | CVE-2019-9295 | Missing Authorization vulnerability in Google Android 10.0 In com.android.apps.tag, there is a possible bypass of user interaction requirements due to a missing permission check. | 4.6 |
2019-09-27 | CVE-2019-9294 | Out-of-bounds Read vulnerability in Google Android 10.0 In libstagefright, there is a possible out of bounds read due to a missing bounds check. | 4.3 |
2019-09-27 | CVE-2019-9293 | Out-of-bounds Read vulnerability in Google Android 10.0 In libstagefright, there is a possible out of bounds read due to a missing bounds check. | 4.3 |
2019-09-27 | CVE-2019-9292 | Externally Controlled Reference to a Resource in Another Sphere vulnerability in Google Android 10.0 In the Activity Manager service, there is a possible information disclosure due to a confused deputy. | 2.1 |
2019-09-27 | CVE-2019-9291 | Allocation of Resources Without Limits or Throttling vulnerability in Google Android 10.0 In Bluetooth, there is a possible remote code execution due to an improper memory allocation. | 6.8 |
2019-09-27 | CVE-2019-9290 | Allocation of Resources Without Limits or Throttling vulnerability in Google Android 10.0 In tzdata there is possible memory corruption due to a mismatch between allocation and deallocation functions. | 4.6 |