Re: Run-time taint support proposal
| From: | Ilia Alshanetsky | Date: | Fri, 15 Dec 2006 23:21:10 +0000 |
| Subject: | Re: Run-time taint support proposal | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26999@lists.php.net to get a copy of this message | ||
On 15-Dec-06, at 6:18 PM, Stanislav Malyshev wrote:
I'd say you have pretty weird code if you do include $_POST['VAR']; and yet people do exactly that.And here is your first exploit, let's say we say mysql_real_escape_string() takes tainted data and makes it untainted, what happens when this "safe" data is passed to exec(). You are going toI'd say you have really weird code if you do mysql_real_escape_string() in order to pass the data to exec() ;)
Bitmask identifying different taint modes. Ilia Alshanetskyneed to deal with different levels of taint-untainted and 1 bit is not going to give you that flexibility. You are going to need an int/long, maybe even a long long.What would be stored in this long long?