User enumeration in authentication mechanisms
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-200.
Summary
Description ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. Resolution ---------- We now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available [here](https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7) for branch 2.10.x and 2.x. Credits ------- I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | lexik/jwt-authentication-bundle (Packagist) | before 2.10.7 | 2.10.7 | Patch available | GHSA-2frx-j9hj-6c65 |
| — | lexik/jwt-authentication-bundle (Packagist) | 2.11.0 to before 2.11.3 | 2.11.3 | Patch available | GHSA-2frx-j9hj-6c65 |
- lexik/jwt-authentication-bundle (Packagist) Vendor— Affected before 2.10.7 Fixed in 2.10.7 Patch available GHSA-2frx-j9hj-6c65
- lexik/jwt-authentication-bundle (Packagist) Vendor— Affected 2.11.0 to before 2.11.3 Fixed in 2.11.3 Patch available GHSA-2frx-j9hj-6c65
Remediation
- Fix · GHSA-2frx-j9hj-6c65 lexik/jwt-authentication-bundle (Packagist) Fixed in 2.10.7 Advisory →
- Fix · GHSA-2frx-j9hj-6c65 lexik/jwt-authentication-bundle (Packagist) Fixed in 2.11.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-2frx-j9hj-6c65
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences