Symfony's incorrect parsing of PATH_INFO can lead to limited authorization bypass
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-foundation Packagist |
|
|
| symfony/symfony Packagist |
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-foundation Packagist |
|
|
| symfony/symfony Packagist |
≥ 2.0.0 · < 5.4.50≥ 6.0.0 · < 6.4.29≥ 7.0.0 · < 7.3.7
|
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Symfony's HttpFoundation component defines an object-oriented layer for the HTTP specification. Starting in version 2.0.0 and prior to version 5.4.50, 6.4.29, and 7.3.7, the `Request` class improperly interprets some `PATH_INFO` in a way that leads to representing some URLs with a path that doesn't start with a `/`. This can allow bypassing some access control rules that are built with this `/`-prefix assumption. Starting in versions 5.4.50, 6.4.29, and 7.3.7, the `Request` class now ensures that URL paths always start with a `/`.
From the CVE record · GitHub_M
Symfony HttpFoundation's Request class can interpret some PATH_INFO values as URL paths that do not start with a slash. An attacker can use such a path to bypass access control rules that assume a slash prefix; the input does not specify authentication or user-interaction requirements.
Check applications using symfony/symfony >=2.0.0 <5.4.50, >=6.0.0 <6.4.29, or >=7.0.0 <7.3.7, or symfony/http-foundation <5.4.50, >=6.0.0 <6.4.29, or >=7.0.0 <7.3.7.