BugTraq
Re: DJB's students release 44 *nix software vulnerability advisories Dec 20 2004 11:14PM
Jonathan T Rockway (jrockw2 uic edu) (7 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 09:22PM
laffer1 (laffer1 mail foolishgames com) (1 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 22 2004 06:06AM
Jonathan Rockway (jrockw2 uic edu)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 09:11PM
Thor (thor hammerofgod com)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:50PM
Dave Holland (dh3 sanger ac uk) (1 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 09:55PM
sean (infamous41md hotpop com)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:34PM
milw0rm Inc. (milw0rm gmail com) (2 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 11:58PM
Jack Lloyd (lloyd randombit net)
Re: DJB's students release 44 *nix software vulnerabilityadvisories Dec 21 2004 09:30PM
Antoine Martin (antoine nagafix co uk) (1 replies)
Re: DJB's students release 44 *nix software vulnerabilityadvisories Dec 22 2004 12:23PM
Chris Paget (ivegotta tombom co uk)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:22PM
Stephen Harris (bugtraq spuddy org)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 08:14PM
Raymond M. Reskusich (reskusic uiuc edu)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 21 2004 07:59PM
David F. Skoll (dfs roaringpenguin com) (2 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 22 2004 03:50AM
Jonathan Rockway (jrockw2 uic edu) (2 replies)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 23 2004 04:49PM
Michal Zalewski (lcamtuf dione ids pl)
Re: DJB's students release 44 *nix software vulnerability advisories Dec 22 2004 05:56PM
Casper Dik Sun COM

>/bin/sh exists to run shell commands. That is the purpose of the
>shell. NASM, on the other hand, is designed to create object files
>from assembly files. If NASM starts running arbitrary code on your
>machine, it's doing something unauthorized. That is a security hole.
>By typing "nasm file.S" you are not intending to authorize the author
>of file.S to take over your account, right?

What other purpose does NASM have other than to compile code
and then, implicitely, run it?

I could buy the argument for a webbrowser or a wordprocessor;
but a assembler or compiler?

>Also, could you please show me this shell script you speak of? All the
>shell scripts I know of that give me root access require me to type the
>root password. If you have found a way around this, then you are
>correct, "every UNIX system on Earth has a remote hole". :)

Any script which exploits a local security hole would do.

>Setting buff[1023] to '\0' is a good idea, since vsnprintf won't do
>that if vsprintf(buff, fmt, args) generates 1024 bytes.

You should have paid better attention in class.

Casper

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus