# CVE-2024-36613: Integer overflow in n/a

> An integer overflow in the FFmpeg DXA demuxer allows attackers to cause a denial-of-service condition or undefined behavior.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jan 2025
- **Updated:** 3 Jan 2025
- **Also known as:** DEBIAN-CVE-2024-36613, GHSA-xqm8-c3rv-5vpf, JLSEC-2025-145, UBUNTU-CVE-2024-36613

## What is CVE-2024-36613?

CVE-2024-36613 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 3 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FFmpeg n6.1.1 has a vulnerability in the DXA demuxer of the libavformat library allowing for an integer overflow, potentially resulting in a denial-of-service (DoS) condition or other undefined behavior.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2024-36613?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2024-36613?

Upgrade to a fixed version.

## Is CVE-2024-36613 being exploited?

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

What it is: CVE-2024-36613 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 3 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36613 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-2024-36613/ (Markdown: https://insights.sbomify.com/CVE-2024-36613/index.md)
```

## Sources

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

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