CVE-2016-1902: Symfony Cryptographic Vulnerability
7.5
CVSS Score
3.0
Basic Information
CVE ID
GHSA ID
EPSS Score
0.59697%
CWE
Published
5/17/2022
Updated
2/8/2024
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
symfony/security-core | composer | >= 2.4.0, < 2.6.13 | 2.6.13 |
symfony/security-core | composer | >= 2.7.0, < 2.7.9 | 2.7.9 |
symfony/security | composer | >= 2.3.0, < 2.3.37 | 2.3.37 |
symfony/security | composer | >= 2.4.0, < 2.6.13 | 2.6.13 |
symfony/security | composer | >= 2.7.0, < 2.7.9 | 2.7.9 |
symfony/symfony | composer | >= 2.3.0, < 2.3.37 | 2.3.37 |
symfony/symfony | composer | >= 2.4.0, < 2.6.13 | 2.6.13 |
symfony/symfony | composer | >= 2.7.0, < 2.7.9 | 2.7.9 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from SecureRandom's fallback mechanism when OpenSSL fails. The advisory explicitly mentions the nextBytes function as the problematic entry point. The Symfony blog post confirms the insecure fallback to PHP's weak PRNG functions (uniqid/mt_rand) in PHP 5.x environments without random_compat. The CWE-332 mapping aligns with insufficient entropy in this PRNG implementation. The GitHub PR #17359 and associated commits show removal of custom RNG logic, confirming this was the vulnerable code path.