CVE-2024-0016
First published: Wed Jan 03 2024(Updated: )
In multiple locations, there is a possible out of bounds read due to a missing bounds check. This could lead to paired device information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
Credit: security@android.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Android | ||
| Android | =11.0 | |
| Android | =12.0 | |
| Android | =12.1 | |
| Android | =13.0 | |
| Android | =14.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-0016?
CVE-2024-0016 is classified as a moderate vulnerability due to its potential for information disclosure.
How do I fix CVE-2024-0016?
To mitigate CVE-2024-0016, ensure you are using the latest version of Google Android that addresses this vulnerability.
What systems are impacted by CVE-2024-0016?
CVE-2024-0016 affects Google Android versions 11.0, 12.0, 12.1, 13.0, and 14.0.
Can CVE-2024-0016 be exploited remotely?
CVE-2024-0016 does not require user interaction for exploitation, making it potentially exploitable remotely.
What kind of data could be exposed due to CVE-2024-0016?
CVE-2024-0016 could lead to the disclosure of paired device information.
- agent/first-publish-date
- agent/type
- agent/references
- agent/description
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/remedy
- agent/severity
- agent/last-modified-date
- agent/event
- agent/softwarecombine
- agent/source
- agent/tags
- collector/android-source
- source/Android
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- vendor/google
- canonical/android
- version/android/11.0
- version/android/12.0
- version/android/12.1
- version/android/13.0
- version/android/14.0