GHSA-7g7c-qhf3-x59p – propel/propel1

Package

Manager: composer
Name: propel/propel1
Vulnerable Version: >=1 <1.7.2

Severity

Level: Critical

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS: N/A pctlN/A

Details

propel/propel1 SQL injection possible with limit() on MySQL 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.

Metadata

Created: 2024-05-20T17:36:28Z
Modified: 2024-05-20T17:36:29Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/05/GHSA-7g7c-qhf3-x59p/GHSA-7g7c-qhf3-x59p.json
CWE IDs: ["CWE-89"]
Alternative ID: N/A
Finding: F297
Auto approve: 1