# CVE-2013-3670: Memory corruption in n/a

> Remote attackers can cause a denial of service via crafted RLE data due to improper API usage in FFmpeg's libavcodec.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 10 Jun 2013
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2013-3670, GHSA-gwv6-2mvw-8hmc

## What is CVE-2013-3670?

CVE-2013-3670 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 10 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The rle_unpack function in vmdav.c in libavcodec in FFmpeg git 20130328 through 20130501 does not properly use the bytestream2 API, which allows remote attackers to cause a denial of service (out-of-bounds array access and application crash) via crafted RLE data.  NOTE: the vendor has listed this as an issue fixed in 1.2.1, but the issue is actually in new code that was not shipped with the 1.2.1 release or any earlier release.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-3670?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2013-3670?

Apply the vendor's patch.

## Is CVE-2013-3670 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3670 and fix it if it is affected.

What it is: CVE-2013-3670 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 10 Jun 2013. 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-2013-3670 in the wild and no public exploit code.

Affected product: Ffmpeg Ffmpeg. 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-2013-3670/ (Markdown: https://insights.sbomify.com/CVE-2013-3670/index.md)
```

## Sources

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

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