MediumGHSA-4vpc-5jx4-cfqgCVE-2019-18886

User enumeration leak using switch user functionality in Symfony

Published 2 Dec 2019 · Updated 8 Nov 2023

Affected packages

symfony/security-httpComposer
Affected
>=4.1.0 <4.2.12
Fixed in
4.2.12
Update to the fixed version for your release line, for example:composer require symfony/security-http:^4.2.12
symfony/security-httpComposer
Affected
>=4.3.0 <4.3.8
Fixed in
4.3.8
Update to the fixed version for your release line, for example:composer require symfony/security-http:^4.3.8
symfony/symfonyComposer
Affected
>=4.1.0 <4.2.12
Fixed in
4.2.12
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.2.12
symfony/symfonyComposer
Affected
>=4.3.0 <4.3.8
Fixed in
4.3.8
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.3.8

Details

An issue was discovered in Symfony 4.2.0 to 4.2.11 and 4.3.0 to 4.3.7. The ability to enumerate users was possible due to different handling depending on whether the user existed when making unauthorized attempts to use the switch users functionality. This is related to symfony/security.

Is GHSA-4vpc-5jx4-cfqg 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.

Scan a project free, no signupOr connect GitHub to scan every repo

References

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