# CVE-2018-6406: Memory corruption in n/a

> Remote attackers can trigger heap-based buffer over-reads and out-of-bounds writes in libwebm via crafted .webm files, causing information leaks or crashes.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 30 Jan 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-929q-cjpr-43v5, UBUNTU-CVE-2018-6406, openSUSE-SU-2018:0359-1, openSUSE-SU-2018:0360-1

## What is CVE-2018-6406?

CVE-2018-6406 is a high-severity memory corruption vulnerability in n/a, published on 30 Jan 2018. 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

The function ParseVP9SuperFrameIndex in common/libwebm_util.cc in libwebm through 2018-01-30 does not validate the child_frame_length data obtained from a .webm file, which allows remote attackers to cause an information leak or a denial of service (heap-based buffer over-read and later out-of-bounds write), or possibly have unspecified other impact.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2018-6406?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chromium` | SUSE:Package Hub 12 | All versions | 64.0.3282.140-49.1 |
| `chromium` | SUSE:Package Hub 12 | All versions | 64.0.3282.140-49.1 |
| `re2` | SUSE:Package Hub 12 | All versions | 20180201-8.1 |
| `re2` | SUSE:Package Hub 12 | All versions | 20180201-8.1 |
| `chromium` | SUSE:Package Hub 12 SP2 | All versions | 64.0.3282.140-49.1 |
| `chromium` | SUSE:Package Hub 12 SP2 | All versions | 64.0.3282.140-49.1 |
| `re2` | SUSE:Package Hub 12 SP2 | All versions | 20180201-8.1 |
| `re2` | SUSE:Package Hub 12 SP2 | All versions | 20180201-8.1 |

Products: Webmproject Libwebm.

## How do I fix CVE-2018-6406?

Apply the vendor's patch.

## Is CVE-2018-6406 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-6548](https://insights.sbomify.com/CVE-2018-6548/): Use after free in n/a (critical 9.8)
- [CVE-2019-9746](https://insights.sbomify.com/CVE-2019-9746/): Null dereference in n/a (high 7.5)
- [CVE-2018-19212](https://insights.sbomify.com/CVE-2018-19212/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6406 and fix it if it is affected.

What it is: CVE-2018-6406 is a high-severity memory corruption vulnerability in n/a, published on 30 Jan 2018. 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-2018-6406 in the wild and no public exploit code.

Affected product: n/a. 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-2018-6406/ (Markdown: https://insights.sbomify.com/CVE-2018-6406/index.md)
```

## Sources

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

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