Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 17 Oct 2012 12:25:28 +0200
From: Matthias Weckbecker <>
Subject: Re: CVE request: ruby file creation due in insertion of illegal NUL character

On Wednesday 17 October 2012 11:44:35 Fabian Keil wrote:
> Daniel Kahn Gillmor <> wrote:
> > On 10/16/2012 08:40 AM, Matthias Weckbecker wrote:
> > > Technically, this would also apply to Perl (at least with 5.12.3).
> >
> > It's also the case with perl 5.14.2 (just tested). :/
> At least for Perl I consider this a feature.

I agree. I also think that an application which lets such things happen (ie
allow arbitrary content to be passed to open()) is rather to blame than the
language (/interpreter) itself. But the same applies to Ruby, IMO.

> The NUL byte is a special character and allows trailing white
> space in the filename that is otherwise stripped. This is
> (more or less) documented in perlopentut(1).
> It also seems unlikely that someone adds NUL bytes to the
> white list of acceptable characters by accident, and if there
> is no white list in the first place, the Perl script probably
> has bigger issues.


> Fabian


Matthias Weckbecker, Senior Security Engineer, SUSE Security Team
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany
Tel: +49-911-74053-0;
SUSE LINUX Products GmbH, GF: Jeff Hawn, HRB 16746 (AG Nuernberg) 

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.