# OSV-2020-607: UNKNOWN READ in WelsDec::CWelsDecoder::DecodeFrame2WithCtx

> An attacker can cause a denial of service via an unknown read vulnerability in the OpenH264 decoder when processing crafted video frames.

- **Severity:** Not scored
- **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:** No
- **Published:** 1 Jul 2020

## What is OSV-2020-607?

OSV-2020-607 is a memory corruption vulnerability in openh264, published on 1 Jul 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

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18864

```
Crash type: UNKNOWN READ
Crash state:
WelsDec::CWelsDecoder::DecodeFrame2WithCtx
WelsDec::CWelsDecoder::DecodeFrame2
WelsDec::CWelsDecoder::DecodeFrameNoDelay
```

## Which versions are affected by OSV-2020-607?

1 open source package ship an affected version, including openh264.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openh264` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-607?

No fix has been published for OSV-2020-607 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-607 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-607 and fix it if it is affected.

What it is: OSV-2020-607 is a memory corruption vulnerability in openh264, published on 1 Jul 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 OSV-2020-607 in the wild and no public exploit code.

Affected packages and fixed versions:
- openh264 (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2020-607/ (Markdown: https://insights.sbomify.com/OSV-2020-607/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-607

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