Heap buffer overflow in Blink in Google Chrome prior to 101.0.4951.41 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Published 2023-07-29 00:15:12
Updated 2024-10-03 14:35:03
Source Chrome
View at NVD,   CVE.org
Vulnerability category: Overflow

Products affected by CVE-2022-4920

Exploit prediction scoring system (EPSS) score for CVE-2022-4920

0.16%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 53 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2022-4920

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
9.6
CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
2.8
6.0
134c704f-9b21-4f2e-91b3-4a467353bcc0 2024-10-03
9.6
CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
2.8
6.0
NIST

CWE ids for CVE-2022-4920

  • A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
    Assigned by: 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary)
  • The product writes data past the end, or before the beginning, of the intended buffer.
    Assigned by: nvd@nist.gov (Primary)

References for CVE-2022-4920

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!