GHSA-jwvj-pwww-3mj5 json
laravel framework Unexpected database bindings via requests
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
This is a follow-up to the security advisory https://github.com/laravel/framework/security/advisories/GHSA-3p32-j457-pg5x which addresses a few additional edge cases.
If a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.
Patch / fix
- packagist laravel/framework 6.20.14, 7.30.4, 8.24.0
Is GHSA-jwvj-pwww-3mj5 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | laravel/framework | >=6.0.0, <6.20.14 >=7.0.0, <7.30.4 >=8.0.0, <8.24.0 |
6.20.14 7.30.4 8.24.0 |
References
Sources
- GitHub Advisory GHSA-jwvj-pwww-3mj5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.