Vulnerability Details : CVE-2017-14775
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
Vulnerability category: Information leak
Products affected by CVE-2017-14775
- cpe:2.3:a:laravel:laravel:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2017-14775
0.29%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 50 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2017-14775
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
4.3
|
MEDIUM | AV:N/AC:M/Au:N/C:P/I:N/A:N |
8.6
|
2.9
|
NIST | |
|
5.9
|
MEDIUM | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
2.2
|
3.6
|
NIST |
CWE ids for CVE-2017-14775
-
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.Assigned by: nvd@nist.gov (Primary)
References for CVE-2017-14775
-
https://laravel-news.com/laravel-v5-5-11
Laravel 5.5.11 Released with a Security Fix - Laravel NewsIssue Tracking;Vendor Advisory
-
https://github.com/laravel/framework/releases/tag/v5.5.10
Release v5.5.10 · laravel/framework · GitHubRelease Notes;Third Party Advisory
-
https://github.com/laravel/framework/pull/21320
[5.5] [Security] Close `remember_me` Timing Attack Vector by mcordingley · Pull Request #21320 · laravel/framework · GitHubIssue Tracking;Mailing List;Third Party Advisory
Jump to