GHSA-XQW3-X93M-887X
Host Placeholders Can Match the Start of the Path in Compiled URL Matchers, Bypassing Path-Based Access Control
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-XQW3-X93M-887X divulgada · CVSS 6.3 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Description
For routes that have a host, `CompiledUrlMatcher` matches the string `$host.'.'.$pathinfo` against the host regexp followed by the path regexp. A host placeholder could match `/`, so it could eat the start of the path, while `UrlMatcher` matches the host and the path separately and finds no route. Rules that look at the path, such as `access_control` entries and the `pattern` of firewalls, judge the real path, so they do not apply, while the controller of the route runs.
With the route `/admin/report/{id}`, the host `app.{domain}` and `access_control: [{ path: ^/admin, roles: ROLE_ADMIN }]`, an anonymous request for `/admin/report/1` is sent to the login page, while one with the host `app` and the path `/x./admin/report/1` reaches the controller, with `domain="/x"`. With the requirement `domain: .+`, the real host name works: `app.example.com` and `/x./admin/report/1` match with `domain="example.com./x"`.
Applications are affected when they have routes with host placeholders protected by path-based rules. With the default requirement, the `Host` must be the host of the route without its last labels, such as `app`: `framework.trusted_hosts` blocks that, while a web server that only serves known names may not, for instance nginx passing the raw `Host` header to FastCGI for a request line that carries an absolute URI. With a requirement that accepts `/`, such as `.+`, the real host name works and `trusted_hosts` does not help.
Resolution
The compiled regexp now captures the path ahead of each host alternative that has placeholders, and checks after the host regexp that the rest of the subject is that path. Since a host cannot contain `/`, the path starts at the first `/`, and host placeholders can no longer match any part of it, whatever their requirements. Valid requests keep the same route and the same parameters, as verified against `UrlMatcher` over eleven million generated cases.
The fix is in the dumper, so an application keeps its vulnerable compiled routes until its cache is cleared. Clear the cache after upgrading.
The patches for this issue are available here https://github.com/symfony/symfony/commit/067cde51e29f6d605de4de53322a02c6e23b5416 for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).
Credits
We would like to thank Vincent Cassiau (CyberVanguard) for reporting the issue and Nicolas Grekas for providing the fix.
We would also like to thank Bruno Dias https://github.com/cx-bruno-dias and Ana Lisboa https://github.com/cx-ana-lisboa from Checkmarx for their help getting a CVE assigned.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistsymfony/routing |
Corregida | 5.4.56, 6.4.50, 7.4.23, 8.1.11 | — | — |
Packagistsymfony/symfony |
Corregida | 5.4.56, 6.4.50, 7.4.23, 8.1.11 | — | — |
5.4.566.4.507.4.238.1.11Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/symfony/symfony/security/advisories/GHSA-xqw3-x93m-887xLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
