GHSA-5pv8-ppvj-4h68 Prevent user enumeration using Guard or the new Authenticator-based Security

• Packagist symfony/security: >= 5.0.0, < 5.2.8 → fixed in 5.2.8 • Packagist symfony/security-guard: >= 2.8.0, < 3.4.48 → fixed in 3.4.48 • Packagist symfony/security-guard: >= 4.0.0, < 4.4.23 → fixed in 4.4.23 • Packagist symfony/security-guard: >= 5.0.0, < 5.2.8 → fixed in 5.2.8 • Packagist symfony/security-core: >= 2.8.0, < 3.4.48 → fixed in 3.4.48 • Packagist symfony/security-core: >= 4.0.0, < 4.4.23 → fixed in 4.4.23 • Packagist symfony/security-core: >= 5.0.0, < 5.2.8 → fixed in 5.2.8 • Packagist lexik/jwt-authentication-bundle: >= 2.0.0, < 2.10.7 → fixed in 2.10.7 • Packagist lexik/jwt-authentication-bundle: >= 2.11.0, < 2.11.3 → fixed in 2.11.3 • Packagist symfony/maker-bundle: >= 1.27.0, < 1.29.2 → fixed in 1.29.2 • Packagist symfony/maker-bundle: >= 1.30.0, < 1.31.1 → fixed in 1.31.1 • Packagist symfony/security-http: >= 5.1.0, < 5.2.8 → fixed in 5.2.8 • Packagist symfony/security: >= 2.8.0, < 3.4.49 → fixed in 3.4.49 • Packagist symfony/security: >= 4.0.0, < 4.4.24 → fixed in 4.4.24 • Packagist symfony/symfony: >= 2.8.0, < 3.4.49 → fixed in 3.4.49 • Packagist symfony/symfony: >= 4.0.0, < 4.4.24 → fixed in 4.4.24 • Packagist symfony/symfony: >= 5.0.0, < 5.2.9 → fixed in 5.2.9

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.