Skip to content
Fencer Intel
high 7.8

CVE-2024-29748 kev in the critical feed json

there is a possible way to bypass due to a logic error in the code.

published 2y ago modified 4mo ago also EUVD-2024-26743

cvss
7.8
version 3.1, CNA
cisa kev
Exploited
added 2024-04-04
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Patch / fix

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

  • Google Android 2024-04-05_patch

Is CVE-2024-29748 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. 0-day patched (Project Zero)
  2. Added to CISA KEV
  3. Published
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
2y ago
Patch by
2024-04-25 (2y ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vendor, product
Android, Pixel
CISA name
Android Pixel Privilege Escalation Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Patched
2024-04-02
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Google Android
  • google pixel

Classification

Weakness
  • CWE-280 Improper Handling of Insufficient Permissions or Privileges
  • CWE-755 Improper Handling of Exceptional Conditions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.