Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-jjx5-fq5g-8xpc

HIGHFix: symfony/symfony#17359

GHSA-jjx5-fq5g-8xpc is a high-severity (CVSS 7.5) CWE-310 vulnerability in symfony/security-core. O3 Security confirms whether GHSA-jjx5-fq5g-8xpc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Symfony Cryptographic Vulnerability

Also known asCVE-2016-1902
Published
May 17, 2022
Updated
Feb 18, 2024
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed

Real-World Exposure

8 pkgs affected
🐘symfony/security-core🐘symfony/security-core🐘symfony/security🐘symfony/security🐘symfony/security🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony

Real-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

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsymfony/security-core2.4.0&&< 2.6.132.6.13
🐘Packagistsymfony/security-core2.7.0&&< 2.7.92.7.9
🐘Packagistsymfony/security2.3.0&&< 2.3.372.3.37
🐘Packagistsymfony/security2.4.0&&< 2.6.132.6.13
🐘Packagistsymfony/security2.7.0&&< 2.7.92.7.9
🐘Packagistsymfony/symfony2.3.0&&< 2.3.372.3.37

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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 GHSA-jjx5-fq5g-8xpc is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jjx5-fq5g-8xpc 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 GHSA-jjx5-fq5g-8xpc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-jjx5-fq5g-8xpc in your dependencies?

O3 detects GHSA-jjx5-fq5g-8xpc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.