Re: Security Audit Priorities
| From: | Tim Düsterhus | Date: | Mon, 25 Sep 2023 15:33:00 +0000 |
| Subject: | Re: Security Audit Priorities | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-121138@lists.php.net to get a copy of this message | ||
Hi
On 9/25/23 10:49, Derick Rethans wrote:
So, if you can suggest an area where doing an external review would have high impact, please reply to this email.Some things from top of my head in arbitrary order. Not all of them are necessarily important themselves per se, but rather intended to spark additional thoughts. - Footguns in the default configuration / tunables / php.ini [1] - MySQL Native Driver - password_* [1] - hash_equals() - ext/json, specifically json_decode() - The CSPRNG (ext/random/csprng.c) - bin2hex, base64_encode [2] - Open-ended: Misuse resistance of existing functions - Is it possible for a user to not properly check a return value and would this result in harm (i.e. should the function throw, but does not yet)? Best regards Tim Düsterhus [1] These tie a little into my https://wiki.php.net/rfc/bcrypt_cost_2023 RFC, which is not code but configuration. [2] Should these be made constant-time / should constant-time implementations always be available? See: https://github.com/paragonie/constant_time_encoding