Staging Environment: Content and features may be unstable or change without notice.

Advisory Weakness Curation

GHSA-g2qj-pmxm-9f8f

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-g2qj-pmxm-9f8f

User enumeration in authentication mechanisms 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 https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011 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.

gitlab/packagist/symfony/security-http/GMS-2021-130

User enumeration in authentication mechanisms 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 https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011 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.

gitlab/packagist/symfony/symfony/GMS-2021-131

User enumeration in authentication mechanisms 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 https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011 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.