Bug 9541

Summary: security suggestion for traceroute
Product: [Retired] Red Hat Linux Reporter: wingc
Component: tracerouteAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: dr, redhat
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-04-03 15:28:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description wingc 2000-02-18 01:22:42 UTC
It would be nice to drop all privileges in traceroute immediately at
program initialization time, rather than after parsing arguments. I can see
where a few buffer overflows were patched in the parser, but why risk the
possibility of another one? (can you be totally sure that all those string
functions in glibc won't break in any way in the future?)

Here is a patch that moves all privileged operations to the beginning of
main(), and then drops all privileges:

http://www.engin.umich.edu/caen/systems/Linux/code/patches/traceroute-1.4a5-paranoid.patch


This breaks the '-d' option to traceroute unless you are root, because only
root can set SO_DEBUG. However, I can't get '-d' to do anything useful here
anyway, so I'm not sure if it really matters.

If '-d' actually does do something useful, I can fix that too, let me know.


Thanks,

Chris Wing
wingc.edu

Comment 1 Bill Nottingham 2000-04-03 15:28:59 UTC
*** Bug 10517 has been marked as a duplicate of this bug. ***

Comment 2 Jeff Johnson 2000-07-19 03:42:40 UTC

*** This bug has been marked as a duplicate of 13466 ***