lists.openwall.net   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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 21 Dec 2004 14:59:15 -0500 (EST)
From: "David F. Skoll" <dfs@...ringpenguin.com>
To: Jonathan T Rockway <jrockw2@....edu>
Cc: bugtraq@...urityfocus.com
Subject: Re: DJB's students release 44 *nix software vulnerability advisories


On Mon, 20 Dec 2004, Jonathan T Rockway wrote:

> Regarding local versus remote, look at it this way:  You have a 100%
> secure system.  Then you install NASM.  Now a user FROM THE NETWORK can
> send you some tainted assembly code for you to assemble and he can
> compromise your account.

That's nonsense.  If you have /bin/sh installed, I can send you a shell
script FROM THE NETWORK that will give me root access if you run it.
Therefore, every UNIX system on Earth has a remote hole, according to
your definition.

> Now in regards to full disclosure, I think you should all be happy
> that we bothered to tell you all about these exploits.  We could
> have selfishly used them to compromise machines, but instead we
> wrote them up and mailed them off to the users and the authors!

Could you have?  How, pray tell, would you compromise a machine with
the NASM exploit?  Even if you have a local account, the NASM exploit
lets you run arbitrary code as... yourself.  Big deal.

--
David.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ