Symfony Vulnerable to Timing Attack
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/symfony Packagist |
|
|
| symfony/form Packagist |
| Product | Affected | Fixed in |
|---|---|---|
| symfony/symfony Packagist |
|
|
| symfony/form Packagist |
≥ 2.3.0 · < 2.3.35≥ 2.4.0 · < 2.6.12≥ 2.7.0 · < 2.7.7
|
| symfony/security-http Packagist |
|
|
| symfony/security Packagist |
|
|
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.
From the CVE record · mitre
Affected Symfony Security and Form components may be vulnerable to timing attacks in remember-me authentication, digest authentication, or the legacy CSRF implementation. A remote attacker might cause unspecified impact; the input does not state whether authentication or user interaction is required.
Check applications using affected Packagist symfony/symfony, symfony/form, or symfony/security versions before 2.3.35, 2.6.12, or 2.7.7, or symfony/security-http versions before 2.6.12 or 2.7.7.