GHSA-wq8p-mqvg-2p5h json
laravel framework SQL Injection via limit and offset functions
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
### Impact Those using SQL Server with Laravel and allowing user input to be passed directly to the limit and offset functions are vulnerable to SQL injection. Other database drivers such as MySQL and Postgres are not affected by this vulnerability.
### Patches This problem has been patched on Laravel versions 6.20.26, 7.30.5, and 8.40.0.
### Workarounds You may workaround this vulnerability by ensuring that only integers are passed to the limit and offset functions, as well as the skip and take functions.
Patch / fix
- packagist laravel/framework 6.20.26, 7.30.5, 8.40.0
Is GHSA-wq8p-mqvg-2p5h 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.26 >=7.0.0, <7.30.5 >=8.0.0, <8.40.0 |
6.20.26 7.30.5 8.40.0 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
Sources
- GitHub Advisory GHSA-wq8p-mqvg-2p5h
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.