Bug 1035212 – CVE-2013-7023 qffmpeg: out of array write in case of realloc failure in libavcodec/parser.c

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 1035212 - (CVE-2013-7023) CVE-2013-7023 qffmpeg: out of array write in case of realloc failure in libavcodec/parser.c

Summary:	CVE-2013-7023 qffmpeg: out of array write in case of realloc failure in libav...

Status:	CLOSED WONTFIX

Aliases:	CVE-2013-7023

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20130922,repor...
Keywords:	Security

Depends On:
Blocks:	1034570
	Show dependency tree / graph

Reported:	2013-11-27 05:07 EST by Ratul Gupta
Modified:	2015-07-31 03:12 EDT (History)
CC List:	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:20 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ratul Gupta 2013-11-27 05:07:37 EST

The libavcodec/parser.c in FFmpeg was found to have a out of array write (on heap) vulnerability in case of realloc failure.

References:
http://seclists.org/oss-sec/2013/q4/341
https://trac.ffmpeg.org/ticket/2982

Commit:
https://github.com/FFmpeg/FFmpeg/commit/f31011e9abfb2ae75bb32bc44e2c34194c8dc40a

Comment 2 Stefan Cornelius 2014-06-10 05:08:20 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.