How severe is CVE-2013-5958?

No CVSS score has been assigned to CVE-2013-5958 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-5958?

CVE-2013-5958 affects the following packages: symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/polyfill (Packagist), symfony/security (Packagist), symfony/security (Packagist), symfony/security (Packagist), and 1 more. Ecosystems affected: Packagist.

How do I fix CVE-2013-5958?

Update symfony/symfony to 2.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5958 is resolved across your whole dependency graph.

How do I detect CVE-2013-5958 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-5958 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2013-5958 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-5958 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-5958?

CVE-2013-5958 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-5958?

CVE-2013-5958 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-5958 published, and has it been updated?

CVE-2013-5958 was published on May 17, 2022 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2013-5958: symfony DoS — Fixed in 2.0.25

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

9 pkgs affected

🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/polyfill🐘symfony/security🐘symfony/security🐘symfony/security+1 more

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 Security component in Symfony 2.0.x before 2.0.25, 2.1.x before 2.1.13, 2.2.x before 2.2.9, and 2.3.x before 2.3.6 allows remote attackers to cause a denial of service (CPU consumption) via a long password that triggers an expensive hash computation, as demonstrated by a PBKDF2 computation, a similar issue to CVE-2013-5750.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/symfony`	≥ 2.0.0&&< 2.0.25	2.0.25`composer require symfony/symfony:^2.0.25`
🐘Packagist	`symfony/symfony`	≥ 2.1.0&&< 2.1.13	2.1.13`composer require symfony/symfony:^2.1.13`
🐘Packagist	`symfony/symfony`	≥ 2.2.0&&< 2.2.9	2.2.9`composer require symfony/symfony:^2.2.9`
🐘Packagist	`symfony/symfony`	≥ 2.3.0&&< 2.3.6	2.3.6`composer require symfony/symfony:^2.3.6`
🐘Packagist	`symfony/polyfill`	≥ 1.0.0&&< 1.10.0	1.10.0`composer require symfony/polyfill:^1.10.0`
🐘Packagist	`symfony/security`	≥ 2.0.0&&< 2.0.25	2.0.25`composer require symfony/security:^2.0.25`

Affected Products

1 product · 53 configurations

Application

symfonysensiolabs

53 versions

2.0.02.0.12.0.22.0.32.0.42.0.52.0.62.0.72.0.82.0.92.0.102.0.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/symfony to 2.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5958 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

The Security component in Symfony 2.0.x before 2.0.25, 2.1.x before 2.1.13, 2.2.x before 2.2.9, and 2.3.x before 2.3.6 allows remote attackers to cause a denial of service (CPU consumption) via a long password that triggers an expensive hash computation, as demonstrated by a PBKDF2 computation, a similar issue to CVE-2013-5750.

O3 Security · Impact-Aware SCA

Is CVE-2013-5958 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2013-5958 — symfony