Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 158684

Summary: CAN-2005-1705 gdb arbitrary command execution
Product: Red Hat Enterprise Linux 4 Reporter: Josh Bressers <bressers>
Component: gdbAssignee: Jeff Johnston <jjohnstn>
Status: CLOSED ERRATA QA Contact: Jay Turner <jturner>
Severity: low Docs Contact:
Priority: medium    
Version: 4.0CC: cagney, jjohnstn, srevivo
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=low,public=20050525,reported=20050520,source=vendorsec
Fixed In Version: RHSA-2005-709 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-05 12:41:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 156322    

Description Josh Bressers 2005-05-24 20:09:59 UTC
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 20:13:39 UTC
This issue should also affect RHEL2.1 and RHEL3

Comment 2 Josh Bressers 2005-07-29 21:06:46 UTC
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 18:26:35 UTC
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 12:41:51 UTC
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.