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 1034565 - (CVE-2013-0873) CVE-2013-0873 qffmpeg: Invalid free in libavcodec/shorten.c due to invalid channel count
CVE-2013-0873 qffmpeg: Invalid free in libavcodec/shorten.c due to invalid ch...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20130213,repor...
: Security
Depends On:
Blocks: 1034570
  Show dependency treegraph
 
Reported: 2013-11-26 01:27 EST by Ratul Gupta
Modified: 2014-06-10 05:08 EDT (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:04 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:37 EST
Common Vulnerabilities and Exposures assigned an identifier CVE-2013-0873 to the following vulnerability:

Name: CVE-2013-0873
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0873
Assigned: 20130107
Reference: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=4f1279154ee9baf2078241bf5619774970d18b25
Reference: http://www.ffmpeg.org/security.html

The read_header function in libavcodec/shorten.c in FFmpeg before 1.1.3 allows remote attackers to have an unspecified impact via an invalid channel count, related to "freeing invalid addresses."
Comment 2 Stefan Cornelius 2014-06-10 05:08:04 EDT
Statement:

The Red Hat Security Response Team has rated this issue as having Moderate 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.