CriticalGHSA-x92h-wmg2-6hp7CVE-2019-10913

Invalid HTTP method overrides allow possible XSS or other attacks in Symfony

Published 2 Dec 2019 · Updated 8 Nov 2023

Affected packages

Affected
>=2.7.0 <2.7.51
Fixed in
2.7.51
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^2.7.51
Affected
>=2.8.0 <2.8.50
Fixed in
2.8.50
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^2.8.50
Affected
>=3.0.0 <3.4.26
Fixed in
3.4.26
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^3.4.26
Affected
>=4.0.0 <4.1.12
Fixed in
4.1.12
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^4.1.12
Affected
>=4.2.0 <4.2.7
Fixed in
4.2.7
Update to the fixed version for your release line, for example:composer require symfony/http-foundation:^4.2.7
Affected
>=2.7.0 <2.7.51
Fixed in
2.7.51
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.7.51
Affected
>=2.8.0 <2.8.50
Fixed in
2.8.50
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.8.50
Affected
>=3.0.0 <3.4.26
Fixed in
3.4.26
Update to the fixed version for your release line, for example:composer require symfony/symfony:^3.4.26
Affected
>=4.0.0 <4.1.12
Fixed in
4.1.12
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.1.12
Affected
>=4.2.0 <4.2.7
Fixed in
4.2.7
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.2.7

Details

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation.

Is GHSA-x92h-wmg2-6hp7 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/http-foundation, and gives you the command that fixes it.

References

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