MediumGHSA-r2rq-3h56-fqm4CVE-2018-11386

Symfony DoS

Published 14 May 2022 · Updated 17 Feb 2024

Affected packages

Affected
>=2.7.0 <2.7.48
Fixed in
2.7.48
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.7.48
Affected
>=2.8.0 <2.8.41
Fixed in
2.8.41
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.8.41
Affected
>=3.3.0 <3.3.17
Fixed in
3.3.17
Update to the fixed version for your release line, for example:composer require symfony/symfony:^3.3.17
Affected
>=3.4.0 <3.4.11
Fixed in
3.4.11
Update to the fixed version for your release line, for example:composer require symfony/symfony:^3.4.11
Affected
>=4.0.0 <4.0.11
Fixed in
4.0.11
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.0.11
Affected
>=2.7.0 <2.7.48
Fixed in
2.7.48
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^2.7.48
Affected
>=2.8.0 <2.8.41
Fixed in
2.8.41
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^2.8.41
Affected
>=3.3.0 <3.3.17
Fixed in
3.3.17
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^3.3.17
Affected
>=3.4.0 <3.4.11
Fixed in
3.4.11
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^3.4.11
Affected
>=4.0.0 <4.0.11
Fixed in
4.0.11
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^4.0.11

Details

An issue was discovered in the HttpFoundation component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. The PDOSessionHandler class allows storing sessions on a PDO connection. Under some configurations and with a well-crafted payload, it was possible to do a denial of service on a Symfony application without too much resources.

Is GHSA-r2rq-3h56-fqm4 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/symfony, and gives you the command that fixes it.

References

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