MediumGHSA-cr49-fx2v-9p57CVE-2013-5958
Symfony Denial of Service Via Long Password Hashing
Published 17 May 2022 · Updated 8 Dec 2024
Affected packages
symfony/symfonyComposer
- Affected
- >=2.0.0 <2.0.25
- Fixed in
- 2.0.25
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.0.25symfony/symfonyComposer
- Affected
- >=2.1.0 <2.1.13
- Fixed in
- 2.1.13
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.1.13symfony/symfonyComposer
- Affected
- >=2.2.0 <2.2.9
- Fixed in
- 2.2.9
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.2.9symfony/symfonyComposer
- Affected
- >=2.3.0 <2.3.6
- Fixed in
- 2.3.6
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.3.6symfony/polyfillComposer
- Affected
- >=1.0.0 <1.10.0
- Fixed in
- 1.10.0
Update to the fixed version for your release line, for example:
composer require symfony/polyfill:^1.10.0symfony/securityComposer
- Affected
- >=2.0.0 <2.0.25
- Fixed in
- 2.0.25
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.0.25symfony/securityComposer
- Affected
- >=2.1.0 <2.1.13
- Fixed in
- 2.1.13
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.1.13symfony/securityComposer
- Affected
- >=2.2.0 <2.2.9
- Fixed in
- 2.2.9
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.2.9symfony/securityComposer
- Affected
- >=2.3.0 <2.3.6
- Fixed in
- 2.3.6
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.3.6Details
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.
Is GHSA-cr49-fx2v-9p57 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/symfony, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2013-5958
- Linkgithub.com/symfony/symfony/issues/11522
- Linkgithub.com/symfony/polyfill/pull/155
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/polyfill/CVE-2013-5958.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2013-5958.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2013-5958.yaml
- Packagegithub.com/symfony/symfony
- Linksymfony.com/blog/security-releases-cve-2013-5958-symfony-2-0-25-2-1-13-2-2-9-and-2-3-6-released
- Linksymfony.com/blog/security-releases-cve-2013-5958-symfony-2-0-25-2-1-13-2-2-9-and-2-3-6-released
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.