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

On Wednesday 17 October 2012 20:14:22 Simon McVittie wrote:
> For Perl, one possibility would be to continue to treat an input of
> "foo\0" as equivalent to "foo" (so that you can use "./ foo \0" to
> mean " foo ", as documented), but disallow NULs anywhere except the
> last position.

Although this is a very elegant solution it's on the other hand probably not
trivially implemented, because NUL is mostly treated as the end of a string.
Simply reading beyond it to check whether there is something else that might
need to be taken into account will likely result in more work for Kurt. ;-)

>     S


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.