|
Secure Programming
RE: Are bad developer libraries the problem with M$ software? Nov 16 2002 01:00AM Michael Howard (mikehow microsoft com) (2 replies) RE: Are bad developer libraries the problem with M$ software? Nov 16 2002 07:03PM Frank Knobbe (fknobbe knobbeits com) (3 replies) Re: Are bad developer libraries the problem with M$ software? Nov 18 2002 07:36PM Casper Dik (Casper Dik Sun COM) (1 replies) Re: Are bad developer libraries the problem with M$ software? Nov 18 2002 11:10PM Andrew Griffiths (andrewg d2 net au) (1 replies) Re: Are bad developer libraries the problem with M$ software? Nov 19 2002 03:25AM Frank Knobbe (fknobbe knobbeits com) (3 replies) Re: Are bad developer libraries the problem with M$ software? Mar 22 2003 09:56AM Casper Dik (Casper Dik Sun COM) Re: Are bad developer libraries the problem with M$ software? Nov 19 2002 10:57PM Andrew Dalgleish (secprog andrewdalgleish dyndns org) (2 replies) Re: Are bad developer libraries the problem with M$ software? Nov 22 2002 03:31PM Frank Knobbe (fknobbe knobbeits com) Re: Are bad developer libraries the problem with M$ software? Nov 22 2002 07:11AM Valdis Kletnieks vt edu Re: Are bad developer libraries the problem with M$ software? Nov 18 2002 11:22PM Andrew Griffiths (andrewg d2 net au) Re: Are bad developer libraries the problem with M$ software? Nov 18 2002 06:54PM John Viega (viega securesoftware com) (2 replies) Re: Are bad developer libraries the problem with M$ software? Nov 18 2002 09:46PM Frank Knobbe (fknobbe knobbeits com) (1 replies) Re: Are bad developer libraries the problem with M$ software? Nov 19 2002 09:31AM Steffen Dettmer (steffen dett de) (1 replies) Re: Are bad developer libraries the problem with M$ software? Nov 22 2002 03:35PM Tim van Erven (tripudium chello nl) Re: Are bad developer libraries the problem with M$ software? Nov 18 2002 06:26PM Götz Babin-Ebell (babinebell trustcenter de) Re: Are bad developer libraries the problem with M$ software? Nov 16 2002 03:29PM Alex Lambert (alambert webmaster com) (1 replies) |
|
|
Privacy Statement |
Alex Lambert wrote:
> > "There is no such thing as dangerous functions, only dangerous
> > developers."*
>
> Perl's print statement is safe, right? No buffer overflows *there*...
>
> print 'Hello, '.$query->param('name');
>
> Except now I'm vulnerable to cross-site scripting :)
Languages which allocate memory automatically generally aren't
vulnerable to buffer overflows. OTOH, they tend to be more susceptible
to DoS attacks. E.g. a function which reads "one line" of input may
just keep reading data until it exhausts available memory.
Also "scripting" languages (those which make extensive use of textual
substitution) tend to be prone to "metacharacter injection" attacks.
This applies heavily to sh/bash/csh/etc (and hence to anything that
uses them, e.g. C's system() function and similar) and substantially
to Tcl (particularly for "eval"). There are also aspects of other
languages for which it's a problem, e.g. perl's backticks and the
open() function.
--
Glynn Clements <glynn.clements (at) virgin (dot) net [email concealed]>
[ reply ]