Bug 114923 (CVE-2003-0618) - CVE-2003-0618 leaks file existance information
Summary: CVE-2003-0618 leaks file existance information
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2003-0618
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-04 16:33 UTC by Mark J. Cox
Modified: 2022-04-29 13:35 UTC (History)
3 users (show)

Fixed In Version: 2.1AS
Clone Of:
Environment:
Last Closed: 2009-08-28 14:16:28 UTC
Embargoed:

Attachments (Terms of Use)

Description Mark J. Cox 2004-02-04 16:33:10 UTC 
CAN-2003-0618 was reported 2003Jul29 to Debian. You can test for the
existance of files even if you don't have permission to do so by using
the suidperl command.

        $ su
        # mkdir ~root/delme; chmod 700 ~root/delme;touch ~root/delme/1
        # exit
        $ suidperl ~root/delme/1
        Script is not setuid/setgid in suidperl
        $ suidperl ~root/delme/2
        Can't open perl script "/root/delme/2": No such file ...

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=220486
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203426

        Affects: 2.1AS 2.1ES 2.1AW 2.1WS (5.6.1) 
        Affects: 3AS 3ES 3WS (5.8.0) 

Debian released an errata for this issue in Feb 2004.
Comment 1 Mark J. Cox 2004-02-09 15:40:57 UTC 
Actually this doesn't affect RHEL3 because the setuid perl package was
not shipped.
Comment 2 Josh Bressers 2005-05-04 22:04:20 UTC 
I did some verification work on this one.  This issue does affect RHEL3.  We may
not have shipped perl-suidperl in the past, we do now.
Comment 3 Jason Vas Dias 2006-04-22 01:24:55 UTC 
fixed with perl-5.6.1-38.EL2_1
Comment 4 Robin Norwood 2006-10-01 23:33:54 UTC 
assigning to rnorwood
Comment 5 Mark J. Cox 2007-07-20 11:47:51 UTC 
that version isn't shipped yet, opening and marking MODIFIED
Comment 6 Tomas Hoger 2009-08-28 14:16:28 UTC 
EL2.1 reached end of life.
Note You need to log in before you can comment on or make changes to this bug.