Affected versions
Version ranges need review.
Composerilluminate/database
- Affected versions
- >= 8.0.0, < 8.40.0
- Fixed version
- 8.40.0
Composerilluminate/database
- Affected versions
- >=4.0.0,<4.0.99|>=4.1.0,<4.1.29
- Fixed version
- Not reported
Composerilluminate/database
- Affected versions
- < 6.20.26
- Fixed version
- 6.20.26
Composerlaravel/framework
- Affected versions
- < 6.20.26
- Fixed version
- 6.20.26
Composerlaravel/framework
- Affected versions
- >=4.0.0,<=4.0.11|>=4.1.0,<=4.1.31|>=4.2.0,<=4.2.22|>=5.0.0,<=5.0.35|>=5.1.0,<=5.1.46|>=5.2.0,<=5.2.45|>=5.3.0,<=5.3.31|>=5.4.0,<=5.4.36|>=5.5.0,<5.5.40|>=5.6.0,<5.6.15
- Fixed version
- Not reported
Composerlaravel/framework
- Affected versions
- >= 8.0.0, < 8.40.0
- Fixed version
- 8.40.0
Description
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.
Links
- https://github.com/advisories/GHSA-4mg9-vhxq-vm7j
- https://github.com/laravel/framework
- https://github.com/laravel/framework/security/advisories/GHSA-4mg9-vhxq-vm7j
- https://laravel.com/docs/5.1/upgrade#upgrade-4.1.29
- https://medium.com/@taylorotwell/laravel-security-release-5-6-15-and-5-5-40-56f1257933a0
- https://packagist.org/packages/illuminate/database
- https://packagist.org/packages/laravel/framework

