HighGHSA-jjx5-fq5g-8xpcCVE-2016-1902
Symfony Cryptographic Vulnerability
Published 17 May 2022 · Updated 18 Feb 2024
Affected packages
symfony/security-coreComposer
- Affected
- >=2.4.0 <2.6.13
- Fixed in
- 2.6.13
Update to the fixed version for your release line, for example:
composer require symfony/security-core:^2.6.13symfony/security-coreComposer
- Affected
- >=2.7.0 <2.7.9
- Fixed in
- 2.7.9
Update to the fixed version for your release line, for example:
composer require symfony/security-core:^2.7.9symfony/securityComposer
- Affected
- >=2.3.0 <2.3.37
- Fixed in
- 2.3.37
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.3.37symfony/securityComposer
- Affected
- >=2.4.0 <2.6.13
- Fixed in
- 2.6.13
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.6.13symfony/securityComposer
- Affected
- >=2.7.0 <2.7.9
- Fixed in
- 2.7.9
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.7.9symfony/symfonyComposer
- Affected
- >=2.3.0 <2.3.37
- Fixed in
- 2.3.37
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.3.37symfony/symfonyComposer
- Affected
- >=2.4.0 <2.6.13
- Fixed in
- 2.6.13
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.6.13symfony/symfonyComposer
- Affected
- >=2.7.0 <2.7.9
- Fixed in
- 2.7.9
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.7.9Details
The nextBytes function in the SecureRandom class in Symfony before 2.3.37, 2.6.x before 2.6.13, and 2.7.x before 2.7.9 does not properly generate random numbers when used with PHP 5.x without the paragonie/random_compat library and the openssl_random_pseudo_bytes function fails, which makes it easier for attackers to defeat cryptographic protection mechanisms via unspecified vectors.
Is GHSA-jjx5-fq5g-8xpc 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
- Advisorynvd.nist.gov/vuln/detail/CVE-2016-1902
- Linkgithub.com/symfony/symfony/pull/17359
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-core/CVE-2016-1902.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2016-1902.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2016-1902.yaml
- Linksymfony.com/cve-2016-1902
- Linkwww.landaire.net/blog/cve-2016-1902-symfony-securerandom
- Linksymfony.com/blog/cve-2016-1902-securerandom-s-fallback-not-secure-when-openssl-fails
- Linkwww.debian.org/security/2016/dsa-3588
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.