CVE-2022-0790

Use After Free in Use after free in Cast UI in Google Chrome prior to 99

Verified by Precogs Threat Research
Last Updated: Nov 21, 2024
Base Score
9.6CRITICAL

Executive Summary

CVE-2022-0790 is a critical severity vulnerability affecting binary-analysis. It is classified as Use After Free. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Google Chrome contains a use-after-free vulnerability in the Cast UI. Attackers trick users into interacting with the Chromecast interface via malicious webpages, triggering memory corruption and arbitrary code execution. Precogs Binary SAST explicitly uncovers memory boundary violations in the GUI subsystem."

Exploit Probability (EPSS)
Low (0.6%)
Public POC
Available
Exploit Probability
High (84%)
Public POC
Available
Affected Assets
binary analysisCWE-416

What is this vulnerability?

CVE-2022-0790 is categorized as a critical Use After Free flaw with a CVSS base score of 9.6. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Use after free in Cast UI in Google Chrome prior to 99.0.4844.51 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially perform a sandbox escape via a crafted HTML page.

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score9.6 (CRITICAL)
Vector StringCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
PublishedApril 5, 2022
Last ModifiedNovember 21, 2024
Related CWEsCWE-416

Impact on Systems

Remote Code Execution: Attackers can overwrite the instruction pointer to redirect execution to malicious shellcode.

Memory Corruption: Overwriting adjacent memory regions can corrupt critical application state, leading to privilege escalation.

Denial of Service: Triggering segmentation faults results in immediate disruption of critical systems.

How to Fix and Mitigate CVE-2022-0790

  1. Apply Vendor Patches: Upgrade affected components to their latest, non-vulnerable versions immediately.
  2. Implement Input Validation: Ensure all user-supplied data is validated, sanitized, and type-checked before processing.
  3. Deploy Runtime Protection: Use Precogs continuous monitoring to detect exploitation attempts in real time.
  4. Audit Dependencies: Review and update all third-party libraries and transitive dependencies.

Defending with Precogs AI

Google Chrome contains a use-after-free vulnerability in the Cast UI. Attackers trick users into interacting with the Chromecast interface via malicious webpages, triggering memory corruption and arbitrary code execution. Precogs Binary SAST explicitly uncovers memory boundary violations in the GUI subsystem.

Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.

Start scanning with Precogs →

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceMemory allocation pointer
VectorPointer is accessed after the memory has been freed
SinkDangling pointer dereference
ImpactMemory corruption, sandbox escape, Remote Code Execution (RCE)

Vulnerable Code Pattern

// ❌ VULNERABLE: Use After Free
char *ptr = malloc(256);
free(ptr);
// Taint sink: accessing freed memory
strcpy(ptr, "Exploit payload");

Secure Code Pattern

// ✅ SECURE: Nullifying pointers
char *ptr = malloc(256);
free(ptr);
// Sanitized state: pointer set to NULL
ptr = NULL;

How Precogs Detects This

Precogs Binary SAST engine identifies dangling pointers and complex use-after-free conditions in compiled rendering engines and system libraries.\n

Related Vulnerabilitiesvia CWE-416

Is your system affected?

Precogs AI detects CVE-2022-0790 in compiled binaries, LLMs, and application layers — even without source code access.