Bug 159655 - CAN-2005-1686 filename format string vulnerability
CAN-2005-1686 filename format string vulnerability
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gedit (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-06-06 12:49 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2005-499
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-13 08:28:08 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-06 12:49:39 EDT
gEdit is prone to a format string vulnerability. Exploitation may occur when the
program is invoked with a filename that includes malicious format specifiers.
This issue could be exploited to corrupt arbitrary regions of memory with
attacker-supplied data, potentially resulting in execution of arbitrary code in
the context of the user running the program.
Comment 1 Josh Bressers 2005-06-06 12:51:11 EDT
This issue should also affect RHEL3 and RHEL2.1
Comment 2 Josh Bressers 2005-06-06 12:52:34 EDT
The following example is available (taken from securityfocus.com)

bash-2.05b#cat fmtexp.c

#include <stdio.h>

printf("hah gedit\n");

bash-2.05b#gcc -o fk fmtexp.c

bash-2.05b#mv fk AA%n%n%n.c

bash-2.05b#gedit AA%n%n%n.c
Comment 3 Josh Bressers 2005-06-06 15:52:07 EDT
This issue does not affect RHEL2.1
Comment 4 Josh Bressers 2005-06-13 08:28:08 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.