Bug 159871 - CAN-2005-1766 HelixPlayer heap overflow
CAN-2005-1766 HelixPlayer heap overflow
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: HelixPlayer (Show other bugs)
All Linux
medium Severity urgent
: ---
: ---
Assigned To: Colin Walters
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-06-08 14:39 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2005-517
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-23 15:31:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-06-08 14:39:44 EDT
+++ This bug was initially created as a clone of Bug #159864 +++

This vulnerability involved a complex interaction between a maliciously created
SMIL file and specifically crafted web server caused a heap overflow in the
error message processing for RealText which could have allowed an attacker to
execute arbitrary code on a customer's machine.

This issue also affects HelixPlayer
Comment 1 Josh Bressers 2005-06-08 14:40:55 EDT
I will attach a patch as soon as I have one.
Comment 2 John (J5) Palmieri 2005-06-13 14:12:45 EDT
RHEL-4 built and symlinked
Comment 3 John (J5) Palmieri 2005-06-14 18:26:38 EDT
Josh are you taking care of teh errata for this?
Comment 4 Josh Bressers 2005-06-14 18:42:21 EDT
Yes, this is RHSA-2005:517, it has already passed QA.  We're just waiting on the
Comment 5 Josh Bressers 2005-06-23 15:04:39 EDT
Lifting embargo
Comment 6 Josh Bressers 2005-06-23 15:31:01 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.