VulnerabilityPublished 5 Apr 2024Updated 21 Oct 2025

CVE-2024-29745: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Exploited in the wild · KEV due 25 Apr 2024 : apply the vendor's fix or mitigations to Google Android now.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 25 Apr 2024 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 5 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 1 day before disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Google Devices
19 Mar 202415:02 UTC, 17 days before disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
4 Apr 2024, 1 day before disclosure
CVE published
on cve.org
5 Apr 202420:02 UTC, t = 0
KEV remediation due
US federal deadline
25 Apr 2024, 20 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Description

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.

Impact

The primary impact of CVE-2024-29745 is the unauthorized disclosure of sensitive information from the Android kernel memory. This could include data such as cryptographic keys, user credentials, or other confidential system information, depending on what uninitialized data is exposed. While the vulnerability does not allow privilege escalation or denial of service, the confidentiality breach can facilitate further attacks or compromise user privacy. Organizations that deploy Android devices in sensitive environments—such as government, finance, healthcare, or critical infrastructure—may face increased risk of data leakage. The requirement for local access limits remote exploitation but does not eliminate risk in scenarios where attackers gain physical access or compromise lower-privileged accounts. The widespread use of Android devices globally means that a large number of endpoints could be affected, increasing the potential attack surface. The absence of known exploits in the wild reduces immediate risk but does not preclude future exploitation once details become more widely available.

Mitigation

To mitigate CVE-2024-29745, organizations and users should apply security patches from Google or device manufacturers as soon as they are released. Until patches are available, limiting local access to devices is critical; this includes enforcing strong device lock mechanisms, restricting physical access, and monitoring for suspicious local activity. Employing mobile device management (MDM) solutions to enforce security policies and detect anomalies can reduce risk. Developers and security teams should audit kernel code for proper initialization of memory buffers to prevent similar issues. Additionally, enabling kernel address space layout randomization (KASLR) and other kernel hardening features can reduce the likelihood of successful exploitation. For high-security environments, consider isolating sensitive Android devices or using hardware-backed security modules to protect critical data. Regularly updating devices and educating users about the risks of local attacks will also help mitigate exposure.

CWE-908Use of Uninitialized Resource (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses or accesses a resource that has not been initialized.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 10:36 UTC

WeaknessesCWE-908

Technical details

References

Community reviews

Related threats