CVE-2016-1902: Symfony Cryptographic Vulnerability

Quick answers

Is CVE-2016-1902 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-1902 being exploited in the wild.

How severe is CVE-2016-1902?

Low severity, with a CVSS score of 3, published 17 May 2022.

Which products and versions are affected?

symfony/security (Packagist) ECOSYSTEM:introduced=2.3.0,fixed=2.3.37; symfony/security-core (Packagist) ECOSYSTEM:introduced=2.4.0,fixed=2.6.13; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.3.0,fixed=2.3.37.

Is there a fix for CVE-2016-1902?

Yes. symfony/security (Packagist): upgrade to 2.3.37 or later; symfony/security-core (Packagist): upgrade to 2.6.13 or later; symfony/symfony (Packagist): upgrade to 2.3.37 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2016-1902?

Check whether you run symfony/security (Packagist), symfony/security-core (Packagist) or symfony/symfony (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• symfony/security (Packagist): upgrade to 2.3.37 or later

  composer require symfony/security:^2.3.37

• symfony/security-core (Packagist): upgrade to 2.6.13 or later

  composer require symfony/security-core:^2.6.13

• symfony/symfony (Packagist): upgrade to 2.3.37 or later

  composer require symfony/symfony:^2.3.37

Affected products

• symfony/security (Packagist) ECOSYSTEM:introduced=2.3.0,fixed=2.3.37
• symfony/security-core (Packagist) ECOSYSTEM:introduced=2.4.0,fixed=2.6.13
• symfony/symfony (Packagist) ECOSYSTEM:introduced=2.3.0,fixed=2.3.37

Identifiers

• CVE-2016-1902
• GHSA-jjx5-fq5g-8xpc