Symfony Cryptographic Vulnerability
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-core Packagist |
|
|
| symfony/security Packagist |
|
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-core Packagist |
|
|
| symfony/security Packagist |
|
≥ 2.7.0 · < 2.7.9
|
| symfony/symfony Packagist |
|
|
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.
From the CVE record · mitre
Symfony’s SecureRandom::nextBytes can generate inadequate random numbers when running on PHP 5.x without paragonie/random_compat and when openssl_random_pseudo_bytes fails. Attackers may be able to defeat cryptographic protection through unspecified vectors. The input does not specify whether authentication, network or local access, or user interaction is required.
Check applications using Packagist symfony/security-core versions >=2.4.0 <2.6.13 or >=2.7.0 <2.7.9, or symfony/security or symfony/symfony versions >=2.3.0 <2.3.37, >=2.4.0 <2.6.13, or >=2.7.0 <2.7.9.