First published: Mon Mar 19 2012(Updated: )
On the Symfony 2.0.x version, there's a security issue that allows access to routes protected by a firewall even when the user is not logged in. Both the Routing component and the Security component uses the path returned by `getPathInfo()` to match a Request. The `getPathInfo()` returns a decoded path, but the Routing component (`Symfony\Component\Routing\Matcher\UrlMatcher`) decodes the path a second time; whereas the Security component, `Symfony\Component\HttpFoundation\RequestMatcher`, does not. This difference causes Symfony 2.0 to be vulnerable to double encoding attacks.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/symfony/symfony | >=2.0.0<2.0.19 | |
composer/symfony/security | >=2.0.0<2.0.19 | |
composer/symfony/http-foundation | >=2.0.0<2.0.19 | |
composer/symfony/routing | >=2.0.0<2.0.19 | |
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 | |
composer/symfony/symfony | >=2.0.0<2.0.19 | 2.0.19 |
composer/symfony/security | >=2.0.0<2.0.19 | 2.0.19 |
composer/symfony/routing | >=2.0.0<2.0.19 | 2.0.19 |
composer/symfony/http-foundation | >=2.0.0<2.0.19 | 2.0.19 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.