Bug #77305 [Com]: sigsev in __memcpy_sse2_unaligned due to sqlite bug

Edit report at https://bugs.php.net/bug.php?id=77305&edit=1 ID: 77305 Comment by: spam2 at rhsoft dot net Reported by: zero_420_ at yahoo dot com Summary: sigsev in __memcpy_sse2_unaligned due to sqlite bug Status: Assigned Type: Bug Package: SQLite related Operating System: Ubuntu PHP Version: 7.2.13 Assigned To: stas Block user comment: N Private report: N New Comment: you can have your arbitrary definitions as you like, for the rest of the world bugs which lead to denial of service are security bugs for shared hosting it is critical when random php code leads to segfaults of the whole service and fpm pools just mask the issue Previous Comments: ------------------------------------------------------------------------ [2018-12-25 11:35:54] cmb@php.net We are assessing security related bug reports according to our security classification document[1]. This report falls in the “Not a security issue” category[2], since it | requires the use of code or settings known to be insecure which is certainly the case for arbitrary SQL injection. This security classification document has been agreed upon via a respective RFC[3]. If you think the security classification is flawed, please bring that up on internals@php.net, since this bug tracker is unsuitable for such discussions. Thanks! [1] <https://wiki.php.net/security> [2] <https://wiki.php.net/security#not_a_security_issue> [3] <https://wiki.php.net/rfc/security-classification> ------------------------------------------------------------------------ [2018-12-24 23:49:17] zero_420_ at yahoo dot com just as @spam2 has stated this is true, and it appears that @cmb is oblivious to the fact that this is far more dangerous than simple sql injection because it can be leveraged by an attacker to execute code on the box locally bypassing security measures like disabled functions, however, as we typically see on most of these reports from the php devs, its almost as if their job titles are downplay anything with a security impact, or just ignore the reports flat out ------------------------------------------------------------------------ [2018-12-24 11:47:54] spam2 at rhsoft dot net there is still a difference between vulerable to sql-injection and be able to crash the service ------------------------------------------------------------------------ [2018-12-24 11:44:56] cmb@php.net > would you care to explain how it is not a security issue, if an > attacker is already able to crash php within this context, it is > not very hard for them to leverage this to bypass the security > mechanisms such as disabled_functions. If an attacker is able to crash PHP within this context, the application is vulnerable to SQL injection, and this is the fault of the application, not of PHP. If the application uses prepared statements with bound variables only (which is recommended anyway[1]), then it is not vulnerable to this kind of attack. [1] <http://php.net/manual/en/security.database.sql-injection.php> ------------------------------------------------------------------------ [2018-12-24 01:53:35] zero_420_ at yahoo dot com mitre has assigned CVE-2018-20346 to this issue in sqlite ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=77305 -- Edit this bug report at https://bugs.php.net/bug.php?id=77305&edit=1