CVE-2013-5958: Possible DOS attack with long user-submitted passwords

Published Oct 10, 2013
·
Updated

Possible DOS attack with long user-submitted passwords

Other sources

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 Software

76 affected componentsFixes available
composer/symfony/security>=2.0.0, <2.0.25, >=2.1.0, <2.1.13, >=2.2.0, <2.2.9, >=2.3.0, <2.3.6
composer/symfony/symfony>=2.0.0, <2.0.25, >=2.1.0, <2.1.13, >=2.2.0, <2.2.9, >=2.3.0, <2.3.6
composer/symfony/polyfill>=1.0.0, <1.10.0
composer/symfony/polyfill-php55>=1.0.0, <1.10.0
composer/symfony/security>=2.3.0<2.3.6
2.3.6
composer/symfony/security>=2.2.0<2.2.9
2.2.9
composer/symfony/security>=2.1.0<2.1.13
2.1.13
composer/symfony/security>=2.0.0<2.0.25
2.0.25
composer/symfony/polyfill>=1.0.0<1.10.0
1.10.0
composer/symfony/symfony>=2.3.0<2.3.6
2.3.6
composer/symfony/symfony>=2.2.0<2.2.9
2.2.9
composer/symfony/symfony>=2.1.0<2.1.13
2.1.13
composer/symfony/symfony>=2.0.0<2.0.25
2.0.25
SensioLabs Symfony=2.0.0
SensioLabs Symfony=2.0.1
SensioLabs Symfony=2.0.2
SensioLabs Symfony=2.0.3
SensioLabs Symfony=2.0.4
SensioLabs Symfony=2.0.5
SensioLabs Symfony=2.0.6
SensioLabs Symfony=2.0.7
SensioLabs Symfony=2.0.8
SensioLabs Symfony=2.0.9
SensioLabs Symfony=2.0.10
SensioLabs Symfony=2.0.11
SensioLabs Symfony=2.0.12
SensioLabs Symfony=2.0.13
SensioLabs Symfony=2.0.14
SensioLabs Symfony=2.0.15
SensioLabs Symfony=2.0.16
SensioLabs Symfony=2.0.17
SensioLabs Symfony=2.0.18
SensioLabs Symfony=2.0.19
SensioLabs Symfony=2.0.20
SensioLabs Symfony=2.0.21
SensioLabs Symfony=2.0.22
SensioLabs Symfony=2.0.23
SensioLabs Symfony=2.0.24
SensioLabs Symfony=2.1.0
SensioLabs Symfony=2.1.1
SensioLabs Symfony=2.1.2
SensioLabs Symfony=2.1.3
SensioLabs Symfony=2.1.4
SensioLabs Symfony=2.1.5
SensioLabs Symfony=2.1.6
SensioLabs Symfony=2.1.7
SensioLabs Symfony=2.1.8
SensioLabs Symfony=2.1.9
SensioLabs Symfony=2.1.10
SensioLabs Symfony=2.1.11
SensioLabs Symfony=2.1.12
SensioLabs Symfony=2.2-dev
SensioLabs Symfony=2.2.0
SensioLabs Symfony=2.2.1
SensioLabs Symfony=2.2.2
SensioLabs Symfony=2.2.3
SensioLabs Symfony=2.2.4
SensioLabs Symfony=2.2.5
SensioLabs Symfony=2.2.6
SensioLabs Symfony=2.2.8
SensioLabs Symfony=2.3.0
SensioLabs Symfony=2.3.1
SensioLabs Symfony=2.3.2
SensioLabs Symfony=2.3.3
SensioLabs Symfony=2.3.4
SensioLabs Symfony=2.3.5
composer/symfony/symfony>=2.0.0, <2.0.25
2.0.25
composer/symfony/symfony>=2.1.0, <2.1.13
2.1.13
composer/symfony/symfony>=2.2.0, <2.2.9
2.2.9
composer/symfony/symfony>=2.3.0, <2.3.6
2.3.6
composer/symfony/polyfill>=1.0.0, <1.10.0
1.10.0
composer/symfony/security>=2.0.0, <2.0.25
2.0.25
composer/symfony/security>=2.1.0, <2.1.13
2.1.13
composer/symfony/security>=2.2.0, <2.2.9
2.2.9
composer/symfony/security>=2.3.0, <2.3.6
2.3.6
composer/symfony/polyfill-php55>=1.0.0, <1.10.0
1.10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.3.6
  2. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.2.9
  3. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.1.13
  4. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.0.25
  5. Upgrade

    Upgrade composer/symfony/polyfill to a version that resolves this vulnerability.

    Fixed in 1.10.0
  6. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.3.6
  7. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.2.9
  8. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.1.13
  9. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.0.25
  10. Upgrade

    Upgrade composer/symfony/polyfill-php55 to a version that resolves this vulnerability.

    Fixed in 1.10.0
  11. Upgrade

    Upgrade Symfony Security to a version that resolves this vulnerability.

    Fixed in 2.0.25
  12. Upgrade

    Upgrade Symfony Security to a version that resolves this vulnerability.

    Fixed in 2.1.13
  13. Upgrade

    Upgrade Symfony Security to a version that resolves this vulnerability.

    Fixed in 2.2.9
  14. Upgrade

    Upgrade Symfony Security to a version that resolves this vulnerability.

    Fixed in 2.3.6

Event History

Oct 10, 2013
Advisory Published
08:30 AM
Data Sourced
via Packagist·08:30 AM
DescriptionSeverityAffected Software
Dec 27, 2014
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-5958?

CVE-2013-5958 has a severity rating of medium, indicating that it allows for potential denial of service attacks under specific conditions.

2

How do I fix CVE-2013-5958?

To fix CVE-2013-5958, update Symfony to versions 2.0.25, 2.1.13, 2.2.9, or 2.3.6 or later.

3

Which versions of Symfony are affected by CVE-2013-5958?

CVE-2013-5958 affects Symfony versions 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.

4

What type of vulnerability is CVE-2013-5958?

CVE-2013-5958 is a denial of service vulnerability caused by handling overly long user-submitted passwords.

5

Is there a workaround for CVE-2013-5958 if I can't update immediately?

A temporary workaround for CVE-2013-5958 involves implementing input validation to restrict password lengths to a reasonable limit.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203