CVE-2024-29748
Android Pixel Privilege Escalation
- Published5 Apr 2024
- Added to CISA KEV4 Apr 2024
- Remediation due25 Apr 2024
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-29748 being actively exploited?
Yes. CVE-2024-29748 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 4 Apr 2024.
How severe is CVE-2024-29748?
CVE-2024-29748 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.67% probability of exploitation.
Which products are affected by CVE-2024-29748?
Affected products include Google Android.
How do I fix CVE-2024-29748?
Upgrade affected software to a fixed version, for example Google Android 2024-04-05 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-29748 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.