User enumeration in authentication mechanisms
Published 17 May 2021 · Updated 2 Dec 2024
Affected packages
- Affected
- >=5.1.0 <5.2.8
- Fixed in
- 5.2.8
composer require symfony/security-http:^5.2.8- Affected
- >=5.1.0 <5.2.8
- Fixed in
- 5.2.8
composer require symfony/symfony:^5.2.8Details
Description -----------
The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.
Resolution ----------
We now ensure that 403s are 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 for branch 3.4.
Credits -------
I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.
Is GHSA-g2qj-pmxm-9f8f in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/security-http, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.