# CVE-2022-3653: Memory corruption in Chrome

> A remote attacker can exploit heap corruption in Chrome's Vulkan component via a crafted HTML page, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Nov 2022
- **Updated:** 12 Nov 2024
- **Also known as:** DEBIAN-CVE-2022-3653, GHSA-r94j-7j3g-wg4f, UBUNTU-CVE-2022-3653

## What is CVE-2022-3653?

CVE-2022-3653 is a high-severity memory corruption vulnerability in Google Chrome, published on 1 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap buffer overflow in Vulkan in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-3653?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2022-3653?

Upgrade to a fixed version.

## Is CVE-2022-3653 being exploited?

There is no known exploitation of CVE-2022-3653 in the wild and no public exploit code.

Public exploit code:

- CVE-2022-3653 just the c++ component in Vulkan for later study (github_poc): https://github.com/SpiralBL0CK/CVE-2022-3653

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3653 and fix it if it is affected.

What it is: CVE-2022-3653 is a high-severity memory corruption vulnerability in Google Chrome, published on 1 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3653 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3653/ (Markdown: https://insights.sbomify.com/CVE-2022-3653/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3653
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3653
- OSV: https://osv.dev/vulnerability/CVE-2022-3653

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3653/
Summaries are generated and may contain mistakes; the official description above is the record.