GHSA-9fwj-9mjf-rhj3 json
laravel-auth0 SDK Vulnerable to Brute Force Authentication Tags of CookieStore Sessions
published last yr. modified 9mo ago
- cvss
- 9.1
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
**Overview** Session cookies of applications using the laravel-auth0 SDK configured with CookieStore have authentication tags that can be brute forced, which may result in unauthorized access.
**Am I Affected?** You are affected by this vulnerability if you meet the following pre-conditions: 1. Applications using laravel-auth0 SDK with version <=7.16.0 2. laravel-auth0 SDK uses the Auth0-PHP SDK with version 8.0.0-BETA1 or higher and below 8.14.0. 3. Session storage configured with CookieStore.
**Fix** Upgrade Auth0/laravel-auth0 to v7.17.0. As an additional precautionary measure, we recommend rotating your cookie encryption keys. Note that once updated, any previous session cookies will be rejected.
**Acknowledgement** Okta would like to thank Félix Charette for discovering this vulnerability.
Patch / fix
- packagist auth0/login 7.17.0
Is GHSA-9fwj-9mjf-rhj3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | auth0/login | <7.17.0 |
7.17.0 |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/auth0/laravel-auth0/commit/be2c59adb476c49945dcc55741a54c7a68c1741d
web
-
github.com
/auth0/laravel-auth0/security/advisories/GHSA-9fwj-9mjf-rhj3
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-47275
advisory
-
github.com
/auth0/laravel-auth0
package
-
github.com
/auth0/laravel-auth0/releases/tag/7.17.0
web
Sources
- GitHub Advisory GHSA-9fwj-9mjf-rhj3
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.