basicsecurity.net
Proof, not just disclosure.
Threats / Android / CVE-2024-29748
CVE-2024-29748 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Android Pixel vulnerability

Android Pixel privilege escalation vulnerability allows attackers to interrupt factory reset operations triggered by device admin apps, potentially maintaining unauthorized access.

Verdict

Today item — known-exploited.

A privilege escalation flaw in Android Pixel's factory reset mechanism enables attackers to bypass device admin controls. Exploitation requires local access but can prevent legitimate device wiping, leaving sensitive data exposed.

CISA KEV Yes · 2024-04-043EPSS 0.0068 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.0068 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Android, Pixel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-280 CWE-280.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I gain code execution on the target Pixel device through initial compromise.
Business
Device is exposed to malware installation and data theft.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I intercept or disrupt the factory reset process initiated by the device administrator.
Business
Remediation efforts by IT administrators fail to remove the compromise.
3

Lateral reach — past segmentation narrative 3

Attacker
I maintain elevated privileges and persistence on the device despite reset attempts.
Business
Attacker retains access to corporate or personal data, extending breach duration and impact.
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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Google_Devices (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by Google_DevicesCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.