Threats / Android / CVE-2024-29745
CVE-2024-29745
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Android Pixel vulnerability
Android Pixel devices contain an information disclosure vulnerability in fastboot firmware that could expose sensitive data during device unlock, flash, or lock operations.
Verdict
Today item — known-exploited.
An information disclosure flaw in Pixel fastboot firmware allows attackers with physical or local access to extract sensitive information from affected devices. The vulnerability has been observed in active exploitation.
CISA KEV Yes · 2024-04-044EPSS 0.00482 (verify live)5CVSS 5.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-04-04).
Probability (EPSS)
EPSS 0.00482 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) · Affected: Android, Pixel. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-908 Use of Uninitialized Resource — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain physical access to an unlocked or powered-on Pixel device and interact with its fastboot interface to extract firmware or system information.
Business
Customer device security is compromised, exposing proprietary firmware details and potentially enabling further attacks on the device ecosystem.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage disclosed information from fastboot to identify device-specific secrets or configuration data that enables bypass of security mechanisms.
Business
Support costs increase due to device compromise incidents; brand trust erodes as security boundaries are circumvented through firmware exposure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by Google_DevicesCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.