Xine is a multimedia player which runs on multiple platforms.
More information is available at:
Remote exploitation of a buffer overflow in version 0.99.2 of xine could
allow execution of arbitrary code.
The vulnerability specifically exists in the PNA_TAG handling code of
the pnm_get_chunk() function. The function does not check the if the
length of an input to be stored in a fixed size buffer is larger than
the buffer size.
Exploitation of this vulnerability allows execution of arbitrary code
with the privileges of the targeted user.
In order to exploit this vulnerability, an attacker would have to
convince the targeted user to open a connection to a malicious PNM
server with xine, using a pnm://address/ URL. Depending on configuration
options, this may be exploitable simply by clicking on a link, or it may
require the user to launch the application, specifically requesting the
iDEFENSE Labs has confirmed the existence of this vulnerability in xine
version 0.99.2. It is suspected that earlier versions of xine also
contain this vulnerability.
This vulnerability also affects MPlayer prior to MPlayer 1.0pre5try2.
iDEFENSE is currently unaware of any effective workarounds for this
xine-lib 1-rc8 was released to address this vulnerability and is
available for download at:
An xine patch for this vulnerability is available at:
An MPlayer patch for this vulnerability is available at:
The Common Vulnerabilities and Exposures (CVE) project has assigned the
names CAN-2004-1187 to these issues. This is a candidate for inclusion
in the CVE list (http://cve.mitre.org), which standardizes names for
12/10/2004 Initial vendor notification
12/11/2004 Initial vendor response
12/21/2004 Public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Copyright © 2004 Verisign, 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
email 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,