GHSA-p62r-7637-3wwc
GHSA-p62r-7637-3wwc · Laravel Hijacked authentication cookies vulnerability
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
Fix available
- Published
- Updated
Stack: php
Affected products and versions
laravel/framework Packagist
- Versions
- v4.0.0
- v4.0.1
- v4.0.10
- v4.0.11
- v4.0.2
- v4.0.3
- v4.0.4
- v4.0.5
- v4.0.6
- v4.0.7
- v4.0.8
- v4.0.9
- v4.1.0
- v4.1.1
- v4.1.10
- v4.1.11
- v4.1.12
- v4.1.13
- v4.1.14
- v4.1.15
- v4.1.16
- v4.1.17
- v4.1.18
- v4.1.19
- v4.1.2
- v4.1.20
- v4.1.21
- v4.1.22
- v4.1.23
- v4.1.24
- v4.1.25
- v4.1.3
- v4.1.4
- v4.1.5
- v4.1.6
- v4.1.7
- v4.1.8
- v4.1.9
- Affected ranges
- ECOSYSTEM: ≥ 4.0.0, < 4.1.26
Update to 4.1.26