GHSA-q4xf-7fw5-4x8v Laravel Hijacked authentication cookies vulnerability
Attackers can maintain persistent access via hijacked remember-me cookies even after password resets or logouts, requiring an upgrade to invalidate stolen sessions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-q4xf-7fw5-4x8v?
GHSA-q4xf-7fw5-4x8v is an authentication bypass vulnerability in illuminate/auth, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Laravel 4.1.26 introduces security improvements for "remember me" cookies. Before this update, if a remember cookie was hijacked by another malicious user, the cookie would remain valid for a long period of time, even after the true owner of the account reset their password, logged out, etc.
This change requires the addition of a new remember_token column to your users (or equivalent) database table. After this change, a fresh token will be assigned to the user each time they login to your application. The token will also be refreshed when the user logs out of the application. The implications of this change are: if a "remember me" cookie is hijacked, simply logging out of the application will invalidate the cookie.
Which versions are affected by GHSA-q4xf-7fw5-4x8v?
2 open source packages ship an affected version, including illuminate/auth.
| Package | Affected | Fixed in |
|---|---|---|
illuminate/auth Packagist | From 4.0.0 | 4.1.26 |
illuminate/auth Packagist | From 4.0.0 | 4.1.26 |
How do I fix GHSA-q4xf-7fw5-4x8v?
Upgrade illuminate/auth to 4.1.26 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is GHSA-q4xf-7fw5-4x8v being exploited?
There is no known exploitation of GHSA-q4xf-7fw5-4x8v in the wild and no public exploit code.