Bug #2472 Updated: poison null byte

From: Date: Sun, 16 Jun 2002 12:59:10 +0000
Subject: Bug #2472 Updated: poison null byte
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-10701@lists.php.net to get a copy of this message
ID: 2472 Updated by: sander@php.net Reported By: kerb@fnusa.com -Status: Open +Status: Bogus Bug Type: Other Operating System: Linux 2.2.12 PHP Version: 3.0.12 New Comment: Thank you for taking the time to report a problem with PHP. Unfortunately, PHP 3 is no longer supported. Please download the latest version of PHP 4 from http://www.php.net/downloads.php If you are able to reproduce the bug with one of the latest versions of PHP, please change the PHP version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of PHP. Previous Comments: ------------------------------------------------------------------------ [1999-10-09 08:31:02] kerb@fnusa.com I'm not sure if you've been notified of this, but the same problem that exists in perl-based CGI scripts involving the "poison null byte" exists in PHP. I was able to POST the following to a script: name=John%00+Q.+Public which should translate to "John Q. Public", although if you post that to a PHP document such as <?php echo "Your name is $name"; ?> it will actually print "Your name is John" and stop there. in perl, I know I can s/%00//ge my URL-encoded strings before I actually decode them, but PHP (from the bit I have used it) decodes all posted variables automatically. For more detail into the inner working of the poison null byte, read Phrack issue 55, article 7: http://www.phrack.com/search.phtml?view&article=p55-7 -Kerb ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=2472&edit=1

« previous php.bugs (#10701) next »