Skip to content

Symfony Cryptographic Vulnerability

High severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated Feb 8, 2024

Package

composer symfony/security (Composer)

Affected versions

>= 2.3.0, < 2.3.37
>= 2.4.0, < 2.6.13
>= 2.7.0, < 2.7.9

Patched versions

2.3.37
2.6.13
2.7.9
composer symfony/security-core (Composer)
>= 2.4.0, < 2.6.13
>= 2.7.0, < 2.7.9
2.6.13
2.7.9
composer symfony/symfony (Composer)
>= 2.3.0, < 2.3.37
>= 2.4.0, < 2.6.13
>= 2.7.0, < 2.7.9
2.3.37
2.6.13
2.7.9

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.

References

Published by the National Vulnerability Database Jun 1, 2016
Published to the GitHub Advisory Database May 17, 2022
Reviewed Jul 31, 2023
Last updated Feb 8, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.169%
(54th percentile)

Weaknesses

CVE ID

CVE-2016-1902

GHSA ID

GHSA-jjx5-fq5g-8xpc

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.