First published: Thu Aug 09 2018(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Laravel Laravel | <=5.5.40 | |
Laravel Laravel | >=5.6.0<=5.6.29 | |
PHPUnit unit testing framework | ||
Apache HTTP server | ||
Laravel web application framework | ||
composer/laravel/framework | >=5.6.0<=5.6.29 | |
composer/laravel/framework | <=5.5.40 | |
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2018-15133 is high with a severity value of 8.1.
CVE-2018-15133 occurs as a result of an unserialize call on a potentially untrusted X-XSRF-TOKEN value.
Laravel Framework versions 5.5.40 and 5.6.x through 5.6.29 are affected by CVE-2018-15133.
To fix CVE-2018-15133, upgrade to Laravel Framework version 5.6.30 or newer. Refer to the official Laravel documentation for the upgrade process.
You can find more information about CVE-2018-15133 in the NIST National Vulnerability Database (NVD), Laravel documentation, and Packet Storm Security website.