full-disclosure - Re: Format String Vulnerabilities in Perl Programs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <122827b90512032244x7b39d05h4c80bf64c3a49a6e@mail.gmail.com>
Date: Sun Dec  4 06:44:37 2005
From: stan.bubrouski at gmail.com (Stan Bubrouski)
Subject: 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/
>