VulnWatch by ve1ve2
medium 5.3

GHSA-h2hg-mfj4-rg7q: `in` / `Rule::in` validation rule bypass via loose comparison

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

https://github.com/laravel/framework/security/advisories/GHSA-h2hg-mfj4-rg7q ↗

repo-advisorycomposerCWE-697securityrepo:laravel/framework

`in` / `Rule::in` validation rule bypass via loose comparison ## Summary The `in` validation rule (and `Rule::in`, and `not_in` via the same code) compares the scalar input to the allowlist with a **non-strict** `in_array()`. PHP 8 then compares numeric strings numerically, so many values that are **not literally in the list** pass validation — including whitespace-padded, leading-zero, signed, and scientific-notation forms, and an embedded newline. The value returned by `validated()` / `valid()` is the **raw, un-canonicalized** input, so the attacker-controlled bytes flow through to the application even though the rule was supposed to constrain them to a fixed set. The array branch of the same method already compares as strings (`array_diff`), so this is an internal inconsistency, not intended behavior. ## Impact Any allowlist of numeric values — feature flags (`in:0,1`), status codes, role/tenant/enum IDs stored as integers may be bypassed with an equivalent-but-not-identical representation. ## Patched Fixed in [#61146](https://github.com/laravel/framework/pull/61146) ## Reported by — Sergey Sannikov, GitHub @semx Affected packages: composer:laravel/framework Patched: laravel/framework >=12.67.0, laravel/framework >=13.26.0

Linked vulnerabilities (1)

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

`in` / `Rule::in` validation rule bypass via loose comparison

CWE: CWE-697Aliases: GHSA-gvpq-g4gw-8p4x, GHSA-hmj2-jgmw-v4m4

Also reported by (2)