Processing control commands:
> notfound -1 5.14.2-16
Bug #689314 {Done: Dominic Hargreaves } [perl] perl: segfaults
when echoing a very long string [CVE-2012-5195]
No longer marked as found in versions perl/5.14.2-16.
--
689314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689314
Debian Bug
Control: notfound -1 5.14.2-16
On Fri, Jan 11, 2013 at 10:24:58AM +0200, Niko Tyni wrote:
> On Sat, Jan 05, 2013 at 04:44:48PM +, Dominic Hargreaves wrote:
>
> > Strangely, when I try and reproduce with a vanilla 5.14.3 build, I
> > get:
> >
> > $ ./perl -e 'print "x"x(2**31)'
> > $ echo $?
On Sat, Jan 05, 2013 at 04:44:48PM +, Dominic Hargreaves wrote:
> Strangely, when I try and reproduce with a vanilla 5.14.3 build, I
> get:
>
> $ ./perl -e 'print "x"x(2**31)'
> $ echo $?
> 0
>
> which seems wrong in a different way...
FWIW, I can reproduce it with an unpatched 5.14.3 on cu
Hi, I have i386 system and perl with amd64 kernel, may be this confused
you?
With amd64 system and perl I cannot reproduce it too.
В Сб., 05/01/2013 в 16:44 +, Dominic Hargreaves пишет:
> On Fri, Jan 04, 2013 at 05:00:24PM +0400, Alexander Kudrevatykh wrote:
> > perl still segfaults with comm
On Fri, Jan 04, 2013 at 05:00:24PM +0400, Alexander Kudrevatykh wrote:
> perl still segfaults with command # perl -e 'print "x"x(2**31)'
> but not segfaults with original command
I can reproduce this on i386, but not amd64.
$ perl -le 'print "v"x(2**31+1) ."=1"'
panic: memory wrap at -e line 1.
Package: perl
Version: 5.14.2-16
Followup-For: Bug #689314
perl still segfaults with command # perl -e 'print "x"x(2**31)'
but not segfaults with original command
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i38
6 matches
Mail list logo
