---
title: "GHSA-7g7c-qhf3-x59p: propel/propel1 SQL injection possible with limit() on MySQL"
url: https://erroneo.us/security/ghsa/GHSA-7g7c-qhf3-x59p/
description: "GHSA-7g7c-qhf3-x59p (critical, Composer (PHP)): propel/propel1 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-7g7c-qhf3-x59p"
license: All rights reserved. Quote with attribution and a link.
---

# GHSA-7g7c-qhf3-x59p: propel/propel1 SQL injection possible with limit() on MySQL

## Affected packages

- Composer (PHP) `propel/propel1` >= 1, <= 1.7.1 → fixed: 1.7.2

## 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 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.

## Sources

- [GitHub Advisory GHSA-7g7c-qhf3-x59p](https://github.com/advisories/GHSA-7g7c-qhf3-x59p)
- [github.com](https://github.com/propelorm/Propel/issues/1052)
- [github.com](https://github.com/propelorm/Propel/pull/1054)
- [github.com](https://github.com/propelorm/Propel/commit/b72093201f8e225410f62a246653ac039e31c90a)
- [github.com](https://github.com/FriendsOfPHP/security-advisories/blob/master/propel/propel1/2018-02-14.yaml)

---
Source page: https://erroneo.us/security/ghsa/GHSA-7g7c-qhf3-x59p/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt