illuminate/auth
Packagist2 known CVEs affecting this package
Aggregated from OSV, GitHub Security Advisories, NVD, and vendor advisories. Each CVE links to its full detail page with vendor advisories, patches, fixed versions, and remediation guidance.
CVEs affecting illuminate/authpage 1 of 1
- CVE-2017-14775MEDIUMCVSS 5.9EG 5.9✓ Fixed in 5.5.102017-09-28
vulnerable: v1.0.0 ... v5.5.2 (108 versions)
Laravel before 5.5.10 mishandles the remember_me token verification process because DatabaseUserProvider does not have constant-time token comparison.
- CVE-2017-9303MEDIUMCVSS 6.1EG 6.1✓ Fixed in 5.4.222017-05-29
vulnerable: v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.9
Laravel 5.4.x before 5.4.22 does not properly constrain the host portion of a password-reset URL, which makes it easier for remote attackers to conduct phishing attacks by specifying an attacker-controlled host.
Check whether illuminate/auth is used in your infrastructure
EchelonGraph scans your cloud and SBOMs to map every package to your actual deployments. See blast radius for illuminate/auth CVEs against the assets you own.
Start Free Scan →