CVE-2024-29745
Google Android
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2024-29745 is a medium-severity Use of Uninitialized Resource (CWE-908) vulnerability in Google Android. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 39th percentile by exploit likelihood (below the median); CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-29745 is an information disclosure vulnerability stemming from the use of uninitialized data, tracked under CWE-908. It affects Pixel devices running Android and was disclosed in the April 2024 Android security bulletin, carrying a CVSS 3.1 score of 5.5 that reflects local attack vector, low complexity, and high impact on confidentiality with no privileges or user interaction required.
A local attacker who already has a presence on the device can exploit the flaw to read sensitive information from uninitialized memory regions. No additional execution privileges or user interaction are needed, allowing the issue to be triggered directly by any process or app running with standard local access.
The official Pixel security bulletin published on 2024-04-01 addresses the issue through platform updates that initialize memory before use. The vulnerability is also listed in CISA's Known Exploited Vulnerabilities catalog, confirming that mitigation via the referenced patches is required for affected devices.
EPSS for the CVE rose from a low baseline to a recorded peak of 0.0118, indicating emerging exploitation interest after public disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-26740
Vulnerability Data
there is a possible Information Disclosure due to uninitialized data. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
- CWE(s)
- KEV Date Added
- 04 April 2024
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.
Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.
Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.
Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.
Application security requirements can specify mandatory initialization of variables and resources before use.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.