CVE-2010-4705: Integer Overflow

Published Jan 22, 2011

Updated

Integer overflow in the vorbisresiduedecodeinternal function in libavcodec/vorbisdec.c in the Vorbis decoder in FFmpeg, possibly 0.6, has unspecified impact and remote attack vectors, related to the sizes of certain integer data types. NOTE: this might overlap CVE-2011-0480.

Affected Software

1 affected component

FFmpeg FFmpeg=0.6

Remediation

Patch Available

http://git.ffmpeg.org/?p=ffmpeg.git;a=commit;h=366d919016a679d3955f6fe5278fa7ce4f47b81e

Event History

Jan 22, 2011

CVE Published

via MITRE·09:00 PM

Data Sourced

via MITRE·09:00 PM

Description

Frequently Asked Questions

What would an attacker need to do to exploit this issue?

The issue has remote attack vectors and affects the Vorbis decoder. An attacker would need to cause a vulnerable FFmpeg instance to decode crafted Vorbis data.

Are systems exposed by default?

Exposure depends on whether the application uses FFmpeg's Vorbis decoder to process attacker-controlled or remotely supplied Vorbis content. The provided data does not identify a specific default configuration.

What should teams do if they cannot patch immediately?

Limit or disable processing of untrusted Vorbis content where possible, especially in services that decode media received remotely. The issue is rated critical with impacts to confidentiality, integrity, and availability.

How can I determine whether an installation is affected?

Check whether the deployed FFmpeg build includes the vulnerable Vorbis decoder code in libavcodec/vorbis_dec.c and whether the fix associated with commit 366d919016a679d3955f6fe5278fa7ce4f47b81e has been applied. The available information only identifies FFmpeg possibly 0.6, so it does not provide a complete affected-version range.

CVE-2010-4705: Integer Overflow

Affected Software

Remediation

Patch Available

Event History

Frequently Asked Questions

What would an attacker need to do to exploit this issue?

Are systems exposed by default?

What should teams do if they cannot patch immediately?

How can I determine whether an installation is affected?

Company

Resources

Contact

Frequently Asked Questions

What would an attacker need to do to exploit this issue?

Are systems exposed by default?

What should teams do if they cannot patch immediately?

How can I determine whether an installation is affected?