bugtraq - Re: Re: Buffer Overflow in ActivePerl?

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: <20040518150739.47371cde.volker.tanger@detewe.de>
Date: Tue, 18 May 2004 15:07:39 +0200
From: "Volker Tanger" <volker.tanger@...ewe.de>
To: Axel Beckert <beckert@...s.de>
Cc: Oliver@...yhat.de, full-disclosure@...ts.netsys.com,
   bugtraq@...urityfocus.com
Subject: Re: Re: Buffer Overflow in ActivePerl?

On Tue, 18 May 2004 11:03:40 +0200 Axel Beckert <beckert@...s.de> wrote:
> Am Mon, May 17, 2004 at 10:23:56PM +0200, Oliver@...yhat.de schrieb:
> > i played around with ActiveState's ActivePerl for Win32, and crashed
> > Perl.exe with the following command:
> > 
> > perl -e "$a="A" x 256; system($a)"

Your command line parameters for perl.exe are probably:
	1.)	-e
	2.)	"$a="
	3.)	A
	4.)	" x 256; system($a)"

Thus are you sure you get $A set with 256 "A"s?

Are you crashing system() or perl.exe's command line parser?

Please define "crashed".

Bye

Volker Tanger
ITK Security

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html