CVE-2016-1902 is a high-severity (CVSS 7.5) CWE-310 vulnerability in symfony/security-core. O3 Security confirms whether CVE-2016-1902 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Symfony Cryptographic Vulnerability
Real-World Exposure
symfony/security-core🐘symfony/security-core🐘symfony/security🐘symfony/security🐘symfony/security🐘symfony/symfony🐘symfony/symfony🐘symfony/symfonyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/security-core | ≥ 2.4.0&&< 2.6.13 | 2.6.13 |
| 🐘Packagist | symfony/security-core | ≥ 2.7.0&&< 2.7.9 | 2.7.9 |
| 🐘Packagist | symfony/security | ≥ 2.3.0&&< 2.3.37 | 2.3.37 |
| 🐘Packagist | symfony/security | ≥ 2.4.0&&< 2.6.13 | 2.6.13 |
| 🐘Packagist | symfony/security | ≥ 2.7.0&&< 2.7.9 | 2.7.9 |
| 🐘Packagist | symfony/symfony | ≥ 2.3.0&&< 2.3.37 | 2.3.37 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update symfony/security-core to 2.6.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1902 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2016-1902 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2016-1902. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2016-1902 in your dependencies?
O3 detects CVE-2016-1902 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.