VulnWatch by ve1ve2
medium 4.8

GHSA-ch34-gjmh-c4hp: Fluent Rule::exists() and Rule::unique() where() values can be interpreted as reserved predicates instead of literal values

Source:
Laravel framework releases (GitHub laravel/framework)
Published:
Fetched:
Updated:
Affects:
laravel laravel/framework

https://github.com/laravel/framework/security/advisories/GHSA-ch34-gjmh-c4hp ↗

repo-advisorycomposersecurityrepo:laravel/framework

Fluent Rule::exists() and Rule::unique() where() values can be interpreted as reserved predicates instead of literal values ### Impact When `Rule::exists()` or `Rule::unique()` is scoped with the fluent `where()` method, the condition is serialized into the string rule format and parsed again. A scalar value of `NULL`, `NOT_NULL`, or one starting with `!` could be evaluated as an IS NULL, IS NOT NULL, or not-equal predicate instead of a literal comparison. If an attacker can influence a scope value, such as a tenant key, and the application relies on the rule to verify ownership of a referenced record, the validation can accept records from other scopes. For `unique`, the scope can be widened. Applications that use independent authorization checks or closure-based `where()` conditions are not affected in the same way. ### Patches A fix that makes the validator read conditions from the rule object so `where()` values are compared literally is proposed in laravel/framework pull requests 62425 (13.x) and 62426 (12.x). ### Workarounds Do not pass user-influenced values to the scalar `where()` form. Use a closure-based `where()` and perform independent ownership authorization of referenced records. Affected packages: composer:laravel/framework Patched: laravel/framework >=13.43.0, laravel/framework >=12.73.0

Linked vulnerabilities (1)

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

Fluent Rule::exists() and Rule::unique() where() values can be interpreted as reserved predicates instead of literal values

Also reported by (2)