Skip to content
Fencer Vulns
high 8.1

CVE-2024-32896 kev in the critical feed json

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

published 2024-06-13 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-30666

cvss
8.1
version 3.1, CNA
cisa kev
Exploited
added 2024-06-13
epss
3.0%
EPSS 3.0% chance of exploitation in 30 days, percentile 87%
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-06-01

Timeline

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

Known exploited

Added
2 y ago
Patch by
2024-07-04 (2 y 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-06-11
Details
project zero tracker

CISA SSVC

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

Exploit prediction

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

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Google Android

Classification

Weakness
  • CWE-783 Operator Precedence Logic Error
  • CWE-670 Always-Incorrect Control Flow Implementation

References

Sources

Fencer Vulns 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.