FLAC Integer Overflow Lets Remote Users Execute Arbitrary Code
SecurityTracker Alert ID: 1018815|
SecurityTracker URL: http://securitytracker.com/id/1018815
(Links to External Site)
Date: Oct 12 2007
Execution of arbitrary code via network, User access via network|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): prior to 1.2.1|
A vulnerability was reported in Free Lossless Audio Codec (FLAC). A remote user can cause arbitrary code to be executed on the target user's system.|
A remote user can create a specially crafted FLAC media file that, when loaded by the target user, will trigger an integer overflow in libFLAC and execute arbitrary code on the target user's system. The code will run with the privileges of the target user.
Winamp is also affected.
The vendor was notified on August 29, 2007.
Sean de Regge reported this vulnerability via iDefense.
A remote user can create a FLAC media file that, when loaded by the target user, will execute arbitrary code on the target user's system.|
The vendor has issued a fixed version (1.2.1).|
Vendor URL: flac.sourceforge.net/ (Links to External Site)
|Underlying OS: Linux (Any), UNIX (Any), Windows (Any)|
This archive entry has one or more follow-up message(s) listed below.|
Source Message Contents
Subject: iDefense Security Advisory 10.11.07: Multiple Vendor FLAC Library|
Multiple Vendor FLAC Library Multiple Integer Overflow Vulnerabilities
iDefense Security Advisory 10.11.07
Oct 11, 2007
Free Lossless Audio Codec (FLAC) is a popular file format for audio data
compression. AOL Corp.'s Winamp media player has support for the FLAC
format. More information about FLAC and Winamp is available at the
Remote exploitation of multiple integer overflow vulnerabilities in
libFLAC, as included with various vendor's software distributions,
allows attackers to execute arbitrary code in the context of the
currently logged in user.
These vulnerabilities specifically exist in the handling of malformed
FLAC media files. In each case, an integer overflow can occur while
calculating the amount of memory to allocate. As such, insufficient
memory is allocated for the data that is subsequently read in from the
file, and a heap based buffer overflow occurs.
Exploitation allows remote attackers to execute arbitrary code in the
context of the user attempting to play the media file. Exploitation
requires that an attacker persuade a targeted user into opening a
malformed FLAC file.
iDefense has confirmed the existence of these vulnerabilities libFLAC
1.2.0, as well as the version of libFLAC included in in the full 5.35
version Winamp. Previous versions of libFLAC may also be vulnerable.
The lite version of Winamp does not include support for the FLAC file
format, and as such is not vulnerable.
For Winamp users, it is possible to remove support for the FLAC file
format by uninstalling the FLAC input plug-in.
VI. VENDOR RESPONSE
The FLAC maintainers have released version 1.2.1 of FLAC to address
these vulnerabilities. AOL Corp. has addressed this vulnerability in
version 5.5 of Winamp. For more information see the FLAC change log at
the following URL.
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2007-4619 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
VIII. DISCLOSURE TIMELINE
08/29/2007 Initial vendor notification
08/29/2007 Initial vendor response
10/11/2007 Coordinated public disclosure
This vulnerability was reported to iDefense by Sean de Regge.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Copyright © 2007 iDefense, Inc.
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically,
please e-mail email@example.com for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct,
indirect, or consequential loss or damage arising from use of, or
reliance on, this information.