[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <122827b90512032244x7b39d05h4c80bf64c3a49a6e@mail.gmail.com>
Date: Sun, 4 Dec 2005 01:44:29 -0500
From: Stan Bubrouski <stan.bubrouski@...il.com>
To: "Michael J. Pomraning" <mjp@...urepipe.com>
Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com,
"Steven M. Christey" <coley@...re.org>
Subject: Re: Re: Format String Vulnerabilities in Perl
Programs
On 12/3/05, Michael J. Pomraning <mjp@...urepipe.com> wrote:
<SNIP>
> For Perl projects, I'd also nominate syslog(), from the standard Sys::Syslog
> module, for special attention. It's common in *NIX environments regardless
> of programmers' backgrounds and is extremely likely to be called with
> untrusted data interpolated directly in the format string argument --
> syslog("info", "A user said $user_input"), for example.
>
This has been mentioned numerous times, including this week (?), nothing new.
-sb
> Regards,
> Mike
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists