# CVE-2020-6413: Security feature bypass in Chrome

> A remote attacker can bypass HTML validators in Google Chrome by using a crafted HTML page, potentially undermining security checks.

- **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:** 11 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-6413, GHSA-pf2w-j9wv-g46c, UBUNTU-CVE-2020-6413

## What is CVE-2020-6413?

CVE-2020-6413 is a high-severity vulnerability in Google Chrome, published on 11 Feb 2020. 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

Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass HTML validators via a crafted HTML page.

## Which versions are affected by CVE-2020-6413?

It affects 2 products.


Products: Google Chrome, Opensuse Backports Sle.

## How do I fix CVE-2020-6413?

Upgrade to a fixed version.

## Is CVE-2020-6413 being exploited?

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

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

What it is: CVE-2020-6413 is a high-severity vulnerability in Google Chrome, published on 11 Feb 2020. 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-2020-6413 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-2020-6413/ (Markdown: https://insights.sbomify.com/CVE-2020-6413/index.md)
```

## Sources

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

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