Security Digest · Vulnerability record · Known exploited
CVE-2024-29748: Android Pixel Privilege Escalation Vulnerability
Exploited in the wild (CISA KEV). there is a possible way to bypass due to a logic error in the code.
CISA KEV · added 2024-04-04 CVSS 7.8 High EPSS 0.7% · p52
Should you act?
Exploited: patch now if you run it
CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Yes, if you run Android Pixel. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2024-04-04, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2024-04-25; treat that as the outer limit, not the target.
- EPSS 0.7%, percentile 52: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 52% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs local access needed. Lower urgency for most teams unless an attacker could already run code on the machine.
What it is
there is a possible way to bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
CISA’s summary
Android Pixel contains a privilege escalation vulnerability that allows an attacker to interrupt a factory reset triggered by a device admin app.
Weakness type: CWE-280.
Product: Android Pixel · Assigned by: Google_Devices · Published: 2024-04-05
Affected and fixed versions
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Android | Android kernel |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADP | 3.1 | 7.8 High | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
- Attack vector: local access needed
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: required (a user must click/open something)
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: added 2024-04-04; federal due date 2024-04-25. Known ransomware use: Unknown.
- CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- CISA SSVC assessment: exploitation active, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.68% probability of exploitation activity in the next 30 days; percentile 52.
Timeline
- — Added to CISA’s Known Exploited Vulnerabilities catalog
- — CVE record published by Google_Devices
- — CISA remediation deadline for US federal agencies
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- Listed in CISA KEV notes (source.android.com) source.android.com
Vulnerability records
- CVE.org record CVE-2024-29748 cve.org
- NVD entry CVE-2024-29748 nvd.nist.gov
Government
Other references from the CVE record and advisory
- source.android.com source.android.com
- twitter.com twitter.com
All exploited Android vulnerabilities · Today’s Security Digest