Bug 1035211 – CVE-2013-7010 qffmpeg: integer overflow and out of array accesses in libavcodec/dsputil.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 1035211 - (CVE-2013-7010) CVE-2013-7010 qffmpeg: integer overflow and out of array accesses in libavcodec/dsputil.c

Summary:	CVE-2013-7010 qffmpeg: integer overflow and out of array accesses in libavcod...

Status:	CLOSED WONTFIX

Aliases:	CVE-2013-7010

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

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

URL:
Whiteboard:	impact=low,public=20130830,reported=2...
Keywords:	Security

Depends On:
Blocks:	1034570
	Show dependency tree / graph

Reported:	2013-11-27 05:07 EST by Ratul Gupta
Modified:	2016-03-04 06:51 EST (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:13 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:30 EST

The libavcodec/dsputil.c in FFmpeg was found to have a integer overflow and out of array accesses vulnerabilities.

The issue is fixed by fixing the signedness in sizeof() comparisons.

References:
http://seclists.org/oss-sec/2013/q4/341

Commit:
https://github.com/FFmpeg/FFmpeg/commit/454a11a1c9c686c78aa97954306fb63453299760

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