GHSA-wwq3-m3j5-wv66: Validation exists rule can be bypassed with integer or boolean input on MySQL/MariaDB
- Published:
- Fetched:
- Updated:
- Affects:
- laravel laravel/framework
https://github.com/laravel/framework/security/advisories/GHSA-wwq3-m3j5-wv66 ↗
Validation exists rule can be bypassed with integer or boolean input on MySQL/MariaDB ### Impact The `exists` and `unique` validation rules passed integer and boolean values from the request unchanged to the database query. On MySQL and MariaDB, comparing a string column with an integer casts the column to a number. As a result, JSON input such as `0`, `false` or `[0]` could satisfy a rule like `required|exists:invites,code` on a non-numeric string column without a valid value. An unauthenticated attacker who can submit JSON could bypass "must reference an existing record" checks. PostgreSQL and SQLite are not affected. Form-encoded input is always a string and is not affected. ### Patches `DatabasePresenceVerifier` now compares integers and booleans as strings. The fixes are merged on the 13.x branch (https://github.com/laravel/framework/pull/62447) and the 12.x branch (https://github.com/laravel/framework/pull/62448). ### Workarounds Add the `string` rule (or `integer`, as appropriate) before `exists` and `unique` rules, or cast the input in `prepareForValidation()`. Affected packages: composer:laravel/framework Patched: laravel/framework >=13.43.0, laravel/framework >=12.73.0