bugtraq - Re: 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: Windows password security audit tool. GUI, reports in PDF.

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

Date: Sun, 4 Dec 2005 01:49:25 -0500 (EST)
From: "Steven M. Christey" <coley@...us.mitre.org>
To: Stan Bubrouski <stan.bubrouski@...il.com>
Cc: "Michael J. Pomraning" <mjp@...urepipe.com>,
	full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com,
	"Steven M. Christey" <coley@...re.org>
Subject: Re: Re: Format String Vulnerabilities in Perl
	Programs



It was mentioned this week, but not in my paper, so it didn't hurt for it
to be mentioned again :)

- Steve


On Sun, 4 Dec 2005, Stan Bubrouski wrote:

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