Google Pixel Firmware Information Disclosure Vulnerability due to Uninitialized Data (CVE-2024-29745)
Executive & SecOps Summary
SECOPS ASSESSMENTGoogle Pixel devices and Android operating system
Local attackers can disclose sensitive system memory information without requiring additional execution privileges or user interaction
Immediately apply the April 2024 Google Pixel security update and upgrade to the latest firmware version
Affected Products & Version Scope
Remediation & Live Workaround Commands
PATCH & WORKAROUND1. Official Patch & Version Upgrade Commands
Apply the latest system updates via the Google Pixel settings menu. For administrators and developers with ADB access, verify the current patch level and flash the latest official factory image using the following commands:
# Check device connection and current security patch level
adb devices
adb shell getprop ro.build.version.security_patch
# Ensure the patch level is '2024-04-01' or later.
# To manually flash the latest firmware (requires unlocked bootloader):
./flash-all.sh2. Temporary Workaround & Hardening Configuration
If immediate patching is not feasible, restrict the installation of untrusted third-party applications. In enterprise environments managed via MDM, enforce policies to disable sideloading and debugging interfaces:
# Disable installation of apps from unknown sources via ADB/MDM
adb shell settings put secure install_non_market_apps 0
# Disable USB debugging to prevent physical/local exploitation vectors
adb shell settings put global adb_enabled 03. Log Audit & IoC Verification Commands
Monitor system logs using logcat to detect potential memory dumping attempts or anomalous system behaviors:
# Monitor real-time logs for uninitialized memory access or suspicious leaks
adb logcat | grep -Ei 'uninitialized|leak|mem_dump|failed syscall'Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot
Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.
Technical Root Cause & Exploitation Mechanics
1. Vulnerability Overview & Root Cause
This vulnerability (CVE-2024-29745) is an information disclosure flaw residing in the firmware and kernel components of Google Pixel devices. The root cause of this vulnerability is the presence of uninitialized data (CWE-908) during memory allocation processes. When memory buffers are reused without being properly zeroed out or initialized, residual data from previously executed processes remains in memory and becomes accessible to lower-privileged user-space applications.
2. Exploitation Mechanics & Attack Scenario
A local attacker with basic execution privileges can trigger specific system calls or API requests to force the allocation and return of uninitialized kernel/firmware memory buffers. This attack requires zero user interaction. By reading the uninitialized buffer, the attacker can extract sensitive remnants of prior operations, such as kernel pointers, memory addresses, or cryptographic keys. This leaked information can be leveraged to bypass modern exploit mitigation techniques like ASLR, facilitating subsequent Local Privilege Escalation (LPE) attacks.
3. Infrastructure & Business Impact
This vulnerability has been added to the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating active exploitation in the wild. In an enterprise environment, if an employee's mobile device is compromised via this vulnerability, malicious local applications can harvest sensitive corporate data, session tokens, and credentials, leading to severe data breaches and unauthorized infrastructure access.
Official Vendor Advisories & References
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.
Frequently Asked SecOps Questions (CVE-2024-29745)
FAQQ1. How critical is CVE-2024-29745 and is it actively exploited in the wild?
CVE-2024-29745 is rated CVSS 5.5 (MEDIUM) with a 30-day EPSS exploitation probability of 0.5%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.
Q2. Which vendors and products are affected by CVE-2024-29745?
Primary impacted vendors include google across android, pixel. Scope summary: All Google Pixel devices running firmware versions prior to the April 2024 Security Patch Level
Q3. What temporary mitigations or workarounds exist for CVE-2024-29745 before patching?
[Mitigation] Immediately apply the April 2024 Google Pixel security update and upgrade to the latest firmware version Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.
Generate an Internal Engineering Notice or CISO Report for CVE-2024-29745
Instantly format this advisory into an executive CISO summary or engineering patch ticket.
🔗 Related Advisories in Similar Stack (google)
View Category →Google Pixel Cellular Modem Privilege Escalation Vulnerability (CVE-2026-58704) Security Advisory
[Affected Scope] Google Pixel devices and Android hardware utilizing specific cellular modem chipsets.
Android Integer Overflow Local Privilege Escalation and Code Execution Vulnerability (CVE-2025-48595)
[Affected Scope] Multiple components within the Android Operating System (OS)
Qualcomm Chipset Memory Corruption Vulnerability via Alignment Miscalculation (CVE-2026-21385) Security Advisory
[Affected Scope] Mobile and embedded devices powered by Qualcomm chipsets running affected Android kernel versions
Google Chrome V8 Out-of-bounds Write Remote Code Execution Advisory (CVE-2026-87491)
[Affected Scope] Google Chrome versions prior to 153.0.8010.36 and Chromium-based browsers
Subscribe to Daily Vulnerability Briefings & KEV Alerts
Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.