CVE-2011-4353
The (1) av_image_fill_pointers, (2) vp5_parse_coeff, and (3) vp6_parse ...
Overview
Description
The (1) av_image_fill_pointers, (2) vp5_parse_coeff, and (3) vp6_parse_coeff functions in FFmpeg 0.5.x before 0.5.7, 0.6.x before 0.6.4, 0.7.x before 0.7.9, and 0.8.x before 0.8.8; and in Libav 0.5.x before 0.5.6, 0.6.x before 0.6.4, and 0.7.x before 0.7.3 allow remote attackers to cause a denial of service (out-of-bounds read) via a crafted VP5 or VP6 stream.
Source: OX vulnerability database
Severity
4.3 · MEDIUM
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/I:N/A:P
Weakness: CWE-119
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 7 fixes
debian 4 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 11 | ffmpeg | 7:2.4.1-1 |
| 12 | ffmpeg | 7:2.4.1-1 |
| 13 | ffmpeg | 7:2.4.1-1 |
| 14 | ffmpeg | 7:2.4.1-1 |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| ffmpeg | 7:2.4.1-1 |
root.io debian 2 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 11 | rootio-ffmpeg | 7:2.4.1-1 |
| 12 | rootio-ffmpeg | 7:2.4.1-1 |
References
- ffmpeg.org http://ffmpeg.org/
- libav.org http://libav.org/
- libav.org http://libav.org/releases/libav-0.5.6.changelog
- libav.org http://libav.org/releases/libav-0.6.4.changelog
- libav.org http://libav.org/releases/libav-0.7.3.changelog
- ubuntu.com http://ubuntu.com/usn/usn-1320-1
- ubuntu.com http://ubuntu.com/usn/usn-1333-1
- www.mandriva.com http://www.mandriva.com/security/advisories?name=MDVSA-2012:074
- www.mandriva.com http://www.mandriva.com/security/advisories?name=MDVSA-2012:075
- www.mandriva.com http://www.mandriva.com/security/advisories?name=MDVSA-2012:076
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.