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

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

From: troelsbay at troelsbay.dk (Troels Bay)
Subject: Buffer Overflow in ActivePerl ?

Hi Stef.

I understood as much as this guy wanted if anyone could reproduce it. 
And I understood that he himself was running an x86-system (which I 
mentioned). And then I just let you know that unix doesn't seem to be 
affected. Sorry if I did anything wrong.


On May 18, 2004, at 07:16, Stef wrote:

> Which part of :
>
>> "i played around with ActiveState's ActivePerl for Win32"
>                                                                 
> ^^^^^^^^^^^^^^^^^^^^
> didn't you understand?
>
> On May 17, 2004, at 7:27 PM, Troels Bay wrote:
>
>>
>> Well, it dosen't do anything on my system (not sure if non-X86 
>> systems are supposed to be affected...). Anyway, it just returns to 
>> the shell.
>>
>> System running:
>> Apple MacOSX 10.3.4 [build 7H56]
>>
>>
>> Chii:~ Tiger$ perl -e "$a="A" x 256; system($a)"
>> Chii:~ Tiger$
>>
>>
>>
>> On May 18, 2004, at 00:44, morning_wood wrote:
>>
>>> Can anybody reproduce this?
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>