|
Bugtraq
mailing list archives
Re: Fix for ssh-1.2.27 symlink/bind problem
From: rhialto () POLDER UBC KUN NL (Olaf Seibert)
Date: Mon, 4 Oct 1999 12:58:42 +0200
On Sat, 2 Oct 1999, Scott Gifford wrote:
+ /* OK, now we know we're in the directory we created. Nobody can
+ * rmdir() this because we are in it. Nobody besides root can have
+ * made a symlink in here, because they wouldn't have permission.
+ * Lookin' good...
+ **/
Actually, a directory *can* be rmdir()ed when it some process' current
directory. You can try that with a couple of shells for instance. But
once the directory is not empty, it cannot be rmdir()ed anymore. Perhaps
you can use that fact to your advantage.
On the other hand, if you're in an rmdir()ed directory, a chdir ("..")
or a rename("somename", "../somename") also don't work, and it looks
like even creation of new files or sockets will fail too, so this could
probably be used as a detection after the fact.
(all this on NetBSD 1.3.3)
-Olaf.
--
___ Olaf 'Rhialto' Seibert - ___ Olaf 'Rhialto' Seibert - rhialto () polder ubc -- If one tells the truth,
\X/ .kun.nl -- one is, sooner or later, to be found out. (Oscar Wilde)
By Date
By Thread
Current thread:
Re: [Fwd: Truth about ssh 1.2.27 vulnerabiltiy] Jeff Long (Sep 30)
|