Bug 165400 - CAN-2005-2102 gaim AIM invalid filename DoS
CAN-2005-2102 gaim AIM invalid filename DoS
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gaim (Show other bugs)
4.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Christopher Aillon
impact=low,public=20050811,reported=2...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-08 16:39 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2005-627
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-09 23:54:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Proposed patch for this issue (1.09 KB, patch)
2005-08-08 16:46 EDT, Josh Bressers
no flags Details | Diff

  None (edit)
Description Josh Bressers 2005-08-08 16:39:15 EDT
3. Daniel Atallah fixed a crash in oscar dealing with invalid file names.  It
is remotely exploitable by anyone sending you a file with a non-utf8 filename.
 It sometimes causes a crash in pango.  It might be depending on the version
of gtk you're using.  And seems to crash Linux machines less than Windows
machines (if ever).  This has not yet been fixed in CVS, but it IS in the wild
and you can get a client from http://www.sevenz.net/ to exploit it.  A patch
is attached.  I haven't actually tested it, so hopefully it still applies.
The logic is kosher.
Comment 1 Josh Bressers 2005-08-08 16:42:28 EDT
This issue also affects RHEL3
Comment 2 Josh Bressers 2005-08-08 16:46:18 EDT
Created attachment 117559 [details]
Proposed patch for this issue
Comment 4 Josh Bressers 2005-08-09 23:33:32 EDT
Lifting embargo
Comment 5 Red Hat Bugzilla 2005-08-09 23:54:16 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.

http://rhn.redhat.com/errata/RHSA-2005-627.html

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