CriticalGHSA-wvj5-r78r-hhfqCVE-2016-2403

Symfony Authentication Bypass

Published 14 May 2022 · Updated 16 Feb 2024

Affected packages

Affected
>=2.8.0 <2.8.6
Fixed in
2.8.6
Update to the fixed version for your release line, for example:composer require symfony/security-core:^2.8.6
Affected
>=3.0.0 <3.0.6
Fixed in
3.0.6
Update to the fixed version for your release line, for example:composer require symfony/security-core:^3.0.6
Affected
>=2.8.0 <2.8.6
Fixed in
2.8.6
Update to the fixed version for your release line, for example:composer require symfony/security:^2.8.6
Affected
>=3.0.0 <3.0.6
Fixed in
3.0.6
Update to the fixed version for your release line, for example:composer require symfony/security:^3.0.6
Affected
>=2.8.0 <2.8.6
Fixed in
2.8.6
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.8.6
Affected
>=3.0.0 <3.0.6
Fixed in
3.0.6
Update to the fixed version for your release line, for example:composer require symfony/symfony:^3.0.6

Details

Symfony before 2.8.6 and 3.x before 3.0.6 allows remote attackers to bypass authentication by logging in with an empty password and valid username, which triggers an unauthenticated bind.

Is GHSA-wvj5-r78r-hhfq 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-core, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.