From: Solar Designer <solar@openwall.com>
To: Paul Szabo <psz@maths.usyd.edu.au>
Cc: bugtraq@securityfocus.com, cliph@isec.pl,
linux-kernel@vger.kernel.org, security@debian.org,
security@isec.pl, vulnwatch@vulnwatch.org
Subject: Re: d_path() truncating excessive long path name vulnerability
Date: Thu, 28 Nov 2002 21:00:41 +0300 [thread overview]
Message-ID: <20021128180041.GA13008@openwall.com> (raw)
In-Reply-To: <200211270204.gAR244k330285@milan.maths.usyd.edu.au>
On Wed, Nov 27, 2002 at 01:04:04PM +1100, Paul Szabo wrote:
> Back in March 2002, Wojciech Purczynski <cliph@isec.pl> wrote (original
> article at http://online.securityfocus.com/archive/1/264117 ):
>
> > Name: Linux kernel
> > Version: up to 2.2.20 and 2.4.18
> > ...
> > In case of excessively long path names d_path kernel internal function
> > returns truncated trailing components of a path name instead of an error
> > value. As this function is called by getcwd(2) system call and
> > do_proc_readlink() function, false information may be returned to
> > user-space processes.
>
> The problem is still present in Debian 2.4.19 kernel. I have not tried 2.5,
> but see nothing relevant in the Changelogs at http://www.kernel.org/ .
FWIW, I've included a workaround for this (covering the getcwd(2) case
only, not other uses of d_path() by the kernel or modules) in 2.2.21-ow1
patch and it went into 2.2.22 release in September.
This kind of proves the need for double-checking newer kernel branches
(2.4.x and 2.5.x currently) for fixes going into what many consider
stable kernels.
--
/sd
next prev parent reply other threads:[~2002-11-28 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 2:04 d_path() truncating excessive long path name vulnerability Paul Szabo
2002-11-28 18:00 ` Solar Designer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-28 21:37 Paul Szabo
2002-03-26 13:40 Wojciech Purczynski
2002-03-28 0:12 ` S/ash
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021128180041.GA13008@openwall.com \
--to=solar@openwall.com \
--cc=bugtraq@securityfocus.com \
--cc=cliph@isec.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=psz@maths.usyd.edu.au \
--cc=security@debian.org \
--cc=security@isec.pl \
--cc=vulnwatch@vulnwatch.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.