CVE-2013-7020 json
The read_header function in libavcodec/ffv1dec.c in FFmpeg before 2.1 does not properly enforce certain bit-count and colorspace constraint…
published 12y ago modified 4mo ago also EUVD-2013-6821
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
The read_header function in libavcodec/ffv1dec.c in FFmpeg before 2.1 does not properly enforce certain bit-count and colorspace constraints, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted FFV1 data.
Patch / fix
- ffmpeg Debian 14, Debian 13, Debian 12 7:2.4.1-1
debian advisories DEBIAN-CVE-2013-7020
Is CVE-2013-7020 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/FFmpeg/FFmpeg/commit/b05cd1ea7e45a836f7f6071a716c38bb30326e0f
issue-tracking, patch
-
openwall.com
/lists/oss-security/2013/12/08/3
mailing-list, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2013/11/26/7
mailing-list, patch, third-party-advisory
-
debian.org
/security/2014/dsa-3027
vendor-advisory, third-party-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2014:227
vendor-advisory, broken-link
-
security.gentoo.org
/glsa/201603-06
vendor-advisory
-
ffmpeg.org
/security.html
vendor-advisory
-
secunia.com
/advisories/61389
third-party-advisory
Sources
- CVE List CVE-2013-7020
- NVD CVE-2013-7020
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.