Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Vuln-Dev
[Top] [All Lists]

Re: DJB's students release 44 *nix software vulnerability advisories

Subject: Re: DJB's students release 44 *nix software vulnerability advisories
Date: Sat, 18 Dec 2004 00:28:02 +0100
On Fri, Dec 17, 2004 at 01:16:44PM +0100, cees-bart wrote:
Most of the 44 posted "security" advisories are about software bugs with 
a very low security risk. See for example the posted bug on NASM 
(http://tigger.uic.edu/~jlongs2/holes/nasm.txt): what's the chance of an 
evil asm file being sent to an ignorant user that calls nasm to compile 
this file?

You are right, that this is very low risk.

And this nasm bug is then called a "remotely exploitable 
security hole".

Obviously it is not. I don't think it is even locally exploitable.

If I mail out a shell script that does "rm -rf $HOME/*", 
this can also be considered a remotely exploitable security hole.

The difference between nasm executing arbitrary code and a shell script
causing a shell to execute "rm -rf $HOME/*" is that the first IS NOT
meant to do that, and the second IS meant to do that. So let's not
compare those two.

Actually while the bug in nasm is very low risk, it is such bugs that
make it difficult to build new software using other software as building
blocks - you would need to audit and fix nasm before you could use it in
an web-to-assembler-gateway :-)

regards,

Marcin
-- 
Marcin Owsiany <marcin@owsiany.pl>              http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216
 
"Every program in development at MIT expands until it can read mail."
                                                              -- Unknown

<Prev in Thread] Current Thread [Next in Thread>