# CVE-2012-0823: Memory corruption in n/a

> Remote attackers can cause a denial of service via corrupt input or specific decoding sequences in the VP8 Codec SDK library.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-0823, GHSA-95hq-f353-7fq8

## What is CVE-2012-0823?

CVE-2012-0823 is a medium-severity memory corruption vulnerability in n/a, published on 23 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VP8 Codec SDK (libvpx) before 1.0.0 "Duclair" allows remote attackers to cause a denial of service (application crash) via (1) unspecified "corrupt input" or (2) by "starting decoding from a P-frame," which triggers an out-of-bounds read, related to "the clamping of motion vectors in SPLITMV blocks".

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-0823?

It affects 1 product.


Products: Webmproject Libvpx.

## How do I fix CVE-2012-0823?

Upgrade to a fixed version.

## Is CVE-2012-0823 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-6349](https://insights.sbomify.com/CVE-2023-6349/): Heap overflow in libvpx (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0823 and fix it if it is affected.

What it is: CVE-2012-0823 is a medium-severity memory corruption vulnerability in n/a, published on 23 Feb 2012. 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-2012-0823 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-2012-0823/ (Markdown: https://insights.sbomify.com/CVE-2012-0823/index.md)
```

## Sources

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

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