Skip to content
Log inStart free trial

CVE-2024-32896

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

High Known exploited
Severity
7.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
2.99%
Chance of exploitation in the next 30 days. Higher than 87.30% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Jun 13, 2024
Weakness
CWE-670 Always-Incorrect Control Flow Implementation
CWE-783 Operator Precedence Logic Error
Fix
None yet
No fixed version published
Exploited in the wild. Android Pixel Privilege Escalation Vulnerability (Android Pixel). Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Due for U.S. federal agencies by Jul 4, 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.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 7.8

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-670: Always-Incorrect Control Flow Implementation

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.

CWE-783: Operator Precedence Logic Error

The product uses an expression in which operator precedence causes incorrect logic to be used.

How to prevent it
  • Implementation: Regularly wrap sub-expressions in parentheses, especially in security-critical code.

References

Advisories

Other links

Timeline

  1. Added to CISA's Known Exploited Vulnerabilities catalog
  2. Published
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vg88-3v92-rjx2
Vyper: Return inside for loop more than 1 level deep
Low Same weakness, CWE-670
GHSA-w5hq-g745-h8pq
uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided
Medium Same weakness, CWE-670
GHSA-q49f-xg75-m9xw
Wasmtime has host panic when Winch compiler executes `table.fill`
High Same weakness, CWE-670
GHSA-9f4w-67g7-mqwv
OpenClaw: Endpoint persists after trust decline, leaking gateway credentials
Medium Same weakness, CWE-670
GHSA-v4wr-j3w6-mxqc
tough terminating targets role delegations are not respected
Medium Same weakness, CWE-670
GHSA-vgf2-gvx8-xwc3
Vyper Does Not Check the Success of Certain Precompile Calls
High Same weakness, CWE-670
GHSA-hm3c-93pg-4cxw
In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring
Medium Same weakness, CWE-670
GHSA-q8hx-mm92-4wvg
wasmtime has a runtime crash when combining tail calls with trapping imports
Medium Same weakness, CWE-670
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor