note 93482 deleted from function.include by danbrown
| From: | danbrown@php.net | Date: | Fri, 11 Sep 2009 22:21:06 +0000 |
| Subject: | note 93482 deleted from function.include by danbrown | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-160480@lists.php.net to get a copy of this message | ||
Note Submitter: Anonymous
----
@Richard (rjw201 at cam dot ac dot uk)
Never, ever, ever, EVER encourage people do use your method and in the future, do a little research
before you post. See, what you have there is one of the most unprofessional and weak methods of
avoiding remote injection ever documented and this is why:
First of all, adding a static file extension may cause issues on the developer side and second, it
can be simply bypassed by a null byte injection.
Here is a link to the Wikipedia entry on the null byte/character.
[http://en.wikipedia.org/wiki/Null_character] It reveals in detail of how this character may be used
to attack the victims site. To cut to the chase, you're specifically looking for the [Security
exploit: Poison null byte] section.