---
title: "GHSA-7vw7-qx38-37vr: Propel2 SQL injection possible with limit() on MySQL"
url: https://erroneo.us/security/ghsa/GHSA-7vw7-qx38-37vr/
description: "GHSA-7vw7-qx38-37vr (critical, Composer (PHP)): Propel2 SQL injection possible with limit() on MySQL. The limit() query method is susceptible to…"
type: advisory
section: "Security Digest"
date_published: 2024-05-20
date_modified: 2024-05-20
publisher: erroneo.us
author: erroneo.us Security Desk
ghsa: "GHSA-7vw7-qx38-37vr"
license: All rights reserved. Quote with attribution and a link.
---

# GHSA-7vw7-qx38-37vr: Propel2 SQL injection possible with limit() on MySQL

## Affected packages

- Composer (PHP) `propel/propel` >= 2.0.0-alpha1, <= 2.0.0-alpha7 → fixed: 2.0.0-alpha8

## Details

The limit() query method is susceptible to catastrophic SQL injection with MySQL. For example, given a model User for a table users: This will drop the users table! The cause appears to be a lack of integer casting of the limit input in either Propel\Runtime\ActiveQuery\Criteria::setLimit() or in Propel\Runtime\Adapter\Pdo\MysqlAdapter::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.

## Sources

- [GitHub Advisory GHSA-7vw7-qx38-37vr](https://github.com/advisories/GHSA-7vw7-qx38-37vr)
- [github.com](https://github.com/propelorm/Propel2/issues/1463)
- [github.com](https://github.com/propelorm/Propel2/pull/1464)
- [github.com](https://github.com/propelorm/Propel2/commit/cd23d7384a15cfe203e23b3a835c8ab1d81d9246)
- [github.com](https://github.com/FriendsOfPHP/security-advisories/blob/master/propel/propel/2018-02-14.yaml)

---
Source page: https://erroneo.us/security/ghsa/GHSA-7vw7-qx38-37vr/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt