Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 might allow remote attackers to have unspecified impact via a timin
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.3.35, 2.7.7, 2.6.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 might allow remote attackers to have unspecified impact via a timing attack involving the (1) Symfony/Component/Security/Http/RememberMe/PersistentTokenBasedRememberMeServices or (2) Symfony/Component/Security/Http/Firewall/DigestAuthenticationListener class in the Symfony Security Component, or (3) legacy CSRF implementation from the Symfony/Component/Form/Extension/Csrf/CsrfProvider/DefaultCsrfProvider class in the Symfony Form component.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- symfony/symfonyPackagist
From 2.3.0 · fixed in 2.3.35
- symfony/symfonyPackagist
From 2.7.0 · fixed in 2.7.7
- symfony/formPackagist
From 2.3.0 · fixed in 2.3.35
- symfony/formPackagist
From 2.4.0 · fixed in 2.6.12
- symfony/formPackagist
From 2.7.0 · fixed in 2.7.7
- symfony/security-httpPackagist
From 2.4.0 · fixed in 2.6.12
- symfony/security-httpPackagist
From 2.7.0 · fixed in 2.7.7
- symfony/securityPackagist
From 2.3.0 · fixed in 2.3.35
- symfony/securityPackagist
From 2.4.0 · fixed in 2.6.12
- symfony/securityPackagist
From 2.7.0 · fixed in 2.7.7
- symfony/symfonyPackagist
From 2.4.0 · fixed in 2.6.12