lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 08 Feb 2010 22:57:15 +0100
From: Krzysztof Halasa <>
To: Thierry Zoller <>
Subject: Re: [Full-disclosure] Samba Remote Zero-Day Exploit

Thierry Zoller <> writes:

> Facts :
> - Several distributions run with vulnerable settings per default
>   if there is a "misconfiguration" it is part of the vendor.
> - Your not supposed to be able to traverse dirs.

What's wrong with creating $HOME/tmp -> /tmp/$USER (not necessarily
with Samba, maybe with xterm or ssh) and then accessing /tmp/$USER via
/host/HOME/tmp? Why is it a problem while "ssh host cat /etc/passwd" is

Can you traverse a directory for which you have no +x right?
Can you, for example, write to a file for which you have no +w right?
Read without +r?

If you can't, maybe it's a (local config?) issue with guest accounts, or
maybe Windows-only (and similar, non-guest) accounts, instead of
permissions and symlinks?

Disabling or limiting symlink creation will not really close the "hole",
the problem is not the symlink but that the user has fs access which he
(or she) should never have.

... unless (obviously) answer to any of the 3 questions is positive
(I haven't checked, to be honest) - is it?

Powered by blists - more mailing lists