MediumGHSA-c2v7-j5gq-wcq4CVE-2017-14775
Laravel Sensitive Data Exposure
Published 17 May 2022 · Updated 16 Feb 2024
Affected packages
laravel/frameworkComposer
- Affected
- <5.5.10
- Fixed in
- 5.5.10
Update to the fixed version for your release line, for example:
composer require laravel/framework:^5.5.10illuminate/authComposer
- Affected
- <5.5.10
- Fixed in
- 5.5.10
Update to the fixed version for your release line, for example:
composer require illuminate/auth:^5.5.10Details
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
Is GHSA-c2v7-j5gq-wcq4 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-2017-14775
- Linkgithub.com/laravel/framework/pull/21320
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/illuminate/auth/CVE-2017-14775.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/laravel/framework/CVE-2017-14775.yaml
- Linkgithub.com/laravel/framework/releases/tag/v5.5.10
- Linklaravel-news.com/laravel-v5-5-11
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.