CVE-2022-4924

Exp

Use after free in WebRTC in Google Chrome prior to 97.0.4692.71 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Published: 2023-07-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-4924 is rated High Exploit Risk (67.2/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.53%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-4924

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.00% 0.53% -0.47%
2 2026-05-24 0.94% 1.00% +0.06%
3 2026-04-22 — 0.94% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-4924

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.6 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 6.0 [email protected]

Weakness enumeration for CVE-2022-4924

OS Trackers for CVE-2022-4924

vendor priority summary link
debian not yet assigned CVE-2022-4924 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-4924
ubuntu medium CVE-2022-4924 medium priority: Ubuntu including 1 source packages (chromium-browser), 7 status rows across 7 suites (bionic, focal, jammy, lunar, trusty, upstream, xenial): ignored 3, not-affected 2, DNE 1, released 1. https://ubuntu.com/security/CVE-2022-4924

Affected software / configurations for CVE-2022-4924

Vendor Product Version Raw CPE
google chrome < 97.0.4692.71 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2022-4924

cvelogic Threat Intelligence