# CVE-2010-4203: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via invalid frames in the WebM libvpx library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 5 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4203, GHSA-v9gv-2chp-hf2r, RHSA-2010:0999

## What is CVE-2010-4203?

CVE-2010-4203 is a critical memory corruption vulnerability in Google Chrome, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WebM libvpx (aka the VP8 Codec SDK) before 0.9.5, as used in Google Chrome before 7.0.517.44, allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via invalid frames.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2010-4203?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libvpx` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-utils` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.0-8.el6_0 |
| `libvpx` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-utils` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.0-8.el6_0 |
| `libvpx` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.0-8.el6_0 |
| `libvpx-utils` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.0-8.el6_0 |

Products: Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, Webmproject Libvpx.

## How do I fix CVE-2010-4203?

Upgrade to a fixed version.

## Is CVE-2010-4203 being exploited?

There is no known exploitation of CVE-2010-4203 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-2010-4203 and fix it if it is affected.

What it is: CVE-2010-4203 is a critical memory corruption vulnerability in Google Chrome, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4203 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-2010-4203/ (Markdown: https://insights.sbomify.com/CVE-2010-4203/index.md)
```

## Sources

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

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