Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1034564 - (CVE-2013-0860) CVE-2013-0860 qffmpeg: NULL pointer dereference in libavcodec/error_resilience.c
CVE-2013-0860 qffmpeg: NULL pointer dereference in libavcodec/error_resilience.c
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20130111,reported=2...
: Security
Depends On:
Blocks: 1034570
  Show dependency treegraph
 
Reported: 2013-11-26 01:27 EST by Ratul Gupta
Modified: 2016-03-04 05:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-10 05:08:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ratul Gupta 2013-11-26 01:27:33 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2013-0860 to the following vulnerability:

Name: CVE-2013-0860
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0860
Assigned: 20130107
Reference: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=3e196e4def03c7a91423803402f84d638d316c33
Reference: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=68a0477bc0af026db971ddba22541029a9e8715b
Reference: http://www.ffmpeg.org/security.html

The ff_er_frame_end function in libavcodec/error_resilience.c in FFmpeg before 1.0.4 and 1.1.x before 1.1.1 does not properly verify that a frame is fully initialized, which allows remote attackers to trigger a NULL pointer dereference via crafted picture data.
Comment 2 Stefan Cornelius 2014-06-10 05:08:02 EDT
Statement:

The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.