Laravel Framework RCE Vulnerability
Published 14 May 2022 · Updated 13 Jan 2025
Affected packages
- Affected
- <=5.5.40
- Fixed in
- No fix released
- Affected
- >=5.6.0 <5.6.30
- Fixed in
- 5.6.30
composer require laravel/framework:^5.6.30Details
In Laravel Framework through 5.5.40 and 5.6.x through 5.6.29, remote code execution might occur as a result of an unserialize call on a potentially untrusted X-XSRF-TOKEN value. This involves the decrypt method in Illuminate/Encryption/Encrypter.php and PendingBroadcast in gadgetchains/Laravel/RCE/3/chain.php in phpggc. The attacker must know the application key, which normally would never occur, but could happen if the attacker previously had privileged access or successfully accomplished a previous attack.
Is GHSA-qvqm-h22r-4cp9 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected laravel/framework, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2018-15133
- Linkgithub.com/laravel/framework/commit/d84cf988ed5d4661a4bf1fdcb08f5073835083a0
- Linkgithub.com/kozmic/laravel-poc-CVE-2018-15133
- Packagegithub.com/laravel/framework
- Linklaravel.com/docs/5.6/upgrade#upgrade-5.6.30
- Linkpacketstormsecurity.com/files/153641/PHP-Laravel-Framework-Token-Unserialize-Remote-Command-Execution.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.