CVE-2013-5958: Symfony Denial of Service Via Long Password Hashing

Quick answers

Is CVE-2013-5958 exploited in the wild?

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

How severe is CVE-2013-5958?

Informational severity, published 17 May 2022.

Which products and versions are affected?

symfony/polyfill (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=1.10.0; symfony/security (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.25; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.25.

Is there a fix for CVE-2013-5958?

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

Am I affected by CVE-2013-5958?

Check whether you run symfony/polyfill (Packagist), symfony/security (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/polyfill (Packagist): upgrade to 1.10.0 or later

  composer require symfony/polyfill:^1.10.0

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

  composer require symfony/security:^2.0.25

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

  composer require symfony/symfony:^2.0.25

Affected products

• symfony/polyfill (Packagist) ECOSYSTEM:introduced=1.0.0,fixed=1.10.0
• symfony/security (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.25
• symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.25

Identifiers

• CVE-2013-5958
• GHSA-cr49-fx2v-9p57