Medium severity · published Sep 28, 2017
CVE-2017-14775
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison
5.9
CVSS
1.2%
EPSS
No
On KEV
Description
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.2% · higher than 68% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
LA
Laravel · Laravel
through 5.5.9 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2017-14775
CVE.org
https://www.cve.org/CVERecord?id=CVE-2017-14775
Issue Tracking
https://github.com/laravel/framework/pull/21320
Release Notes
https://github.com/laravel/framework/releases/tag/v5.5.10
Issue Tracking
https://laravel-news.com/laravel-v5-5-11
More from Laravel
8.1
CVE-2018-15133
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
9.8
CVE-2021-28254
A deserialization vulnerability in the destruct() function of Laravel v8.5.9 allows attackers to execute arbitrary commands
9.8
CVE-2022-2870
A vulnerability was found in laravel 5.1 and classified as problematic
8.8
CVE-2022-2886
A vulnerability, which was classified as critical, was found in Laravel 5.1
7.5
CVE-2020-24941
An issue was discovered in Laravel before 6.18.35 and 7.x before 7.24.0