CVE-2013-7009 json
The rpza_decode_stream function in libavcodec/rpza.c in FFmpeg before 2.1 does not properly maintain a pointer to pixel data, which allows…
published 12y ago modified 4mo ago also EUVD-2013-6810
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
The rpza_decode_stream function in libavcodec/rpza.c in FFmpeg before 2.1 does not properly maintain a pointer to pixel data, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Apple RPZA data.
Patch / fix
- ffmpeg Debian 14, Debian 13, Debian 12 7:2.4.1-1
debian advisories DEBIAN-CVE-2013-7009
Is CVE-2013-7009 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.64% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/FFmpeg/FFmpeg/commit/3819db745da2ac7fb3faacb116788c32f4753f34 referenced PoC, tagged "exploit" by a source, unverified
- trac.ffmpeg.org https://trac.ffmpeg.org/ticket/2850 referenced PoC, tagged "exploit" by a source, unverified
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/3819db745da2ac7fb3faacb116788c32f4753f34
exploit, patch
-
openwall.com
/lists/oss-security/2013/12/08/3
mailing-list, patch
-
openwall.com
/lists/oss-security/2013/11/26/7
mailing-list, patch
-
trac.ffmpeg.org
/ticket/2850
exploit
-
security.gentoo.org
/glsa/201603-06
vendor-advisory
- ffmpeg.org /security.html
Sources
- CVE List CVE-2013-7009
- NVD CVE-2013-7009
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.