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

> Attackers can execute arbitrary SQL commands via the limit() method in Propel2, leading to data modification or deletion.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2024

## What is GHSA-7vw7-qx38-37vr?

GHSA-7vw7-qx38-37vr is a SQL injection vulnerability in propel/propel, published on 20 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

## Which versions are affected by GHSA-7vw7-qx38-37vr?

2 open source packages ship an affected version, including propel/propel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `propel/propel` | Packagist | From 2.0.0-alpha1 | 2.0.0-alpha8 |
| `propel/propel` | Packagist | From 2.0.0-alpha1 | 2.0.0-alpha8 |

## How do I fix GHSA-7vw7-qx38-37vr?

Upgrade propel/propel to 2.0.0-alpha8 or later.

## Is GHSA-7vw7-qx38-37vr being exploited?

There is no known exploitation of GHSA-7vw7-qx38-37vr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7vw7-qx38-37vr and fix it if it is affected.

What it is: GHSA-7vw7-qx38-37vr is a SQL injection vulnerability in propel/propel, published on 20 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-7vw7-qx38-37vr in the wild and no public exploit code.

Affected packages and fixed versions:
- propel/propel (Packagist): affected from 2.0.0-alpha1; fixed in 2.0.0-alpha8
- propel/propel (Packagist): affected from 2.0.0-alpha1; fixed in 2.0.0-alpha8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-7vw7-qx38-37vr/ (Markdown: https://insights.sbomify.com/GHSA-7vw7-qx38-37vr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7vw7-qx38-37vr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-7vw7-qx38-37vr/
Summaries are generated and may contain mistakes; the official description above is the record.