Bug 158684 - CAN-2005-1705 gdb arbitrary command execution
CAN-2005-1705 gdb arbitrary command execution
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gdb (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jeff Johnston
Jay Turner
: Security
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-05-24 16:09 EDT by Josh Bressers
Modified: 2015-01-07 19:10 EST (History)
3 users (show)

See Also:
Fixed In Version: RHSA-2005-709
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 08:41:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:709 qe-ready SHIPPED_LIVE Low: gdb security update 2005-10-05 00:00:00 EDT

  None (edit)
Description Josh Bressers 2005-05-24 16:09:59 EDT
gdb before 6.3 searches the current working directory to load the
.gdbinit configuration file, which allows local users to execute
arbitrary commands as the user running gdb.

More information can be found in the gentoo BTS:
Comment 1 Josh Bressers 2005-05-24 16:13:39 EDT
This issue should also affect RHEL2.1 and RHEL3
Comment 2 Josh Bressers 2005-07-29 17:06:46 EDT
Has this fix made it into the RHEL3 U6 update?

jakub has these fixes in the binutils update for RHEL3U6 and RHEL4U2, so I
believe even if we're not ready for U6, we can move forward with a patch.
Comment 3 Jeff Johnston 2005-10-04 14:26:35 EDT
This has been fixed in gdb errata gdb- and is in the current
releases RHEL3U6 and RHEL4U2.
Comment 4 Red Hat Bugzilla 2005-10-05 08:41:51 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.