Chrome OOB Write via Streams API <125.0.6422.141
CVE-2024-5499 Published on May 30, 2024

Out of bounds write in Streams API in Google Chrome prior to 125.0.6422.141 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

NVD

Vulnerability Analysis

CVE-2024-5499 can be exploited with network access, requires user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to be very high.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
REQUIRED
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
HIGH

Weakness Type

What is a Memory Corruption Vulnerability?

The software writes data past the end, or before the beginning, of the intended buffer. Typically, this can result in corruption of data, a crash, or code execution. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent write operation then produces undefined or unexpected results.

CVE-2024-5499 has been classified to as a Memory Corruption vulnerability or weakness.


Products Associated with CVE-2024-5499

stack.watch emails you whenever new vulnerabilities are published in Google Chrome or Fedora Project Fedora. Just hit a watch button to start following.

 
 

Affected Versions

Google Chrome: google chrome:

Exploit Probability

EPSS
1.31%
Percentile
79.57%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.