First published: Thu Sep 21 2017(Updated: )
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/laravel/framework | >=4.1.26<=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.10 | |
composer/illuminate/auth | >=4.1.26<=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.10 | |
composer/laravel/framework | <5.5.10 | 5.5.10 |
Laravel Laravel | <=5.5.9 | |
composer/illuminate/auth | <5.5.10 | 5.5.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-14775 has a medium severity rating due to its potential for timing attacks against the remember_me token.
To fix CVE-2017-14775, upgrade to Laravel version 5.5.10 or higher.
CVE-2017-14775 affects Laravel versions prior to 5.5.10, including 4.x and 5.4.
CVE-2017-14775 is caused by the DatabaseUserProvider not using constant-time comparison for remember_me token verification.
Using Laravel versions below 5.5.10 poses a security risk due to the vulnerability in token handling.