Home page logo
/

fulldisclosure logo Full Disclosure mailing list archives

Re: Python 2.5 (Modules/zlib) minigzip local buffer overflow vulnerability
From: Valdis.Kletnieks () vt edu
Date: Thu, 15 Mar 2007 10:48:55 -0400

On Thu, 15 Mar 2007 14:16:41 +0200, Ismail =?utf-8?q?D=C3=B6nmez?= said:
str{cpy,cat,...} which don't take an size attribute should be removed from 
standard libc, I don't see why people still insist on using this insecure 
variants.

Although it may come as a surprise to some, not all software has to worry
about working in a security-critical environment.  Quite often, the program
is a one-off that's working with data that is relatively trustable, and there
is little or no chance of the software being compromised.  And keep in mind
that str* functions *can* be used safely if somebody did a strlen() check
earlier in the program.

I mean, come *ON*.  If there exists a black hat that can drop an exploit
string into the middle of a data file produced by some data-mining program
of ours, and exploit a program that *didn't even exist* when the data was
written.....  in that case, we're screwed anyhow.  There's no way to stop
a black hat that knows how to exploit code from the future.

Attachment: _bin
Description:

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]