GHSA-7g7c-qhf3-x59p
GHSA-7g7c-qhf3-x59p · propel/propel1 SQL injection possible with limit() on MySQL
Esta página presenta datos de fuentes públicas de vulnerabilidades. Consulta el aviso original antes de actualizar.
The limit() query method is susceptible to catastrophic SQL injection with MySQL. For example, given a model User for a table users: ``` UserQuery::create()->limit('1;DROP TABLE users')->find(); ``` This will drop the users table! The cause appears to be a lack of integer casting of the limit input in either Criteria::setLimit() or in DBMySQL::applyLimit(). The code comments there seem to imply that casting was avoided due to overflow issues with 32-bit integers. This is surprising behavior since one of the primary purposes of an ORM is to prevent basic SQL injection. This affects all versions of Propel: 1.x, 2.x, and 3.
CVSS 9.8 · Crítica · Corrección disponible
- Publicación
- Actualización
Pila tecnológica: php
Productos y versiones afectados
propel/propel1 Packagist
- Versiones
- 1.6.2
- 1.6.3
- 1.6.4
- 1.6.5
- 1.6.6
- 1.6.7
- 1.6.8
- 1.6.9
- 1.7.0
- 1.7.1
- Intervalos de versiones afectados
- ECOSYSTEM: ≥ 1, < 1.7.2
Actualiza a 1.7.2
Fuentes originales
- https://github.com/propelorm/Propel/issues/1052
- https://github.com/propelorm/Propel/pull/1054
- https://github.com/propelorm/Propel/commit/b72093201f8e225410f62a246653ac039e31c90a
- https://github.com/FriendsOfPHP/security-advisories/blob/master/propel/propel1/2018-02-14.yaml
- https://github.com/propelorm/Propel
- https://osv.dev/vulnerability/GHSA-7g7c-qhf3-x59p