HighGHSA-q8hg-pf8v-cxrvCVE-2019-18887

Symfony Http-Kernel has non-constant time comparison in UriSigner

Published 26 Mar 2022 · Updated 20 Feb 2024

Affected packages

Affected
>=2.2.0 <2.8.52
Fixed in
2.8.52
Update to the fixed version for your release line, for example:composer require symfony/http-kernel:^2.8.52
Affected
>=3.0.0 <3.4.35
Fixed in
3.4.35
Update to the fixed version for your release line, for example:composer require symfony/http-kernel:^3.4.35
Affected
>=4.0.0 <4.2.12
Fixed in
4.2.12
Update to the fixed version for your release line, for example:composer require symfony/http-kernel:^4.2.12
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/http-kernel:^4.3.8
Affected
>=2.2.0 <2.8.52
Fixed in
2.8.52
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.8.52
Affected
>=3.0.0 <3.4.35
Fixed in
3.4.35
Update to the fixed version for your release line, for example:composer require symfony/symfony:^3.4.35
Affected
>=4.0.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
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

When checking the signature of an URI (an ESI fragment URL for instance), the URISigner did not used a constant time string comparison function, resulting in a potential remote timing attack vulnerability.

Is GHSA-q8hg-pf8v-cxrv 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-kernel, and gives you the command that fixes it.

References

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