Laravel TokenGuard authentication bypass through non-string API credentials
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| laravel | framework | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Laravel | Framework |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-f9x3-7vq9-cph6 | Laravel TokenGuard authentication bypass through non-string API credentials |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.8% (1.840% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Laravel
Laravel framework |
|
| Vendors & Products |
Laravel
Laravel framework |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Laravel is a web application framework. Prior to 12.68.0 and 13.29.0, TokenGuard configured as a standard token-based API guard does not reject a crafted non-string credential. Under affected MySQL or MariaDB configurations, the authentication lookup can match an unintended existing user, allowing an unauthenticated attacker to bypass authentication and take over an account on routes protected by TokenGuard. This issue is fixed in versions 12.68.0 and 13.29.0. | |
| Title | Laravel TokenGuard authentication bypass through non-string API credentials | |
| Weaknesses | CWE-1287 CWE-287 |
|
| References |
|
|
| Metrics |
cvssV4_0
|