# CVE-2022-3308: Security feature bypass in Chrome

> A remote attacker can escape the browser sandbox via a crafted HTML page, potentially executing code with higher privileges.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **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:** 6 May 2025
- **Also known as:** DEBIAN-CVE-2022-3308, GHSA-qm27-xfxw-qqmp, UBUNTU-CVE-2022-3308

## What is CVE-2022-3308?

CVE-2022-3308 is a high-severity 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

Insufficient policy enforcement in developer tools in Google Chrome prior to 106.0.5249.62 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

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

It affects 1 product.


Products: Google Chrome.

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

Upgrade to a fixed version.

## Is CVE-2022-3308 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3308 exists.

## 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-3308 and fix it if it is affected.

What it is: CVE-2022-3308 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3308 exists.

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-3308/ (Markdown: https://insights.sbomify.com/CVE-2022-3308/index.md)
```

## Sources

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

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