| Package | Affected versions | Patched versions |
|---|---|---|
| symfony/http-kernel | ≥ 7.4.0, < 7.4.12≥ 8.0.0, < 8.0.12 | 7.4.128.0.12 |
| symfony/security-http | ≥ 7.4.0, < 7.4.12≥ 8.0.0, < 8.0.12 | 7.4.128.0.12 |
| symfony/symfony | ≥ 7.4.0, < 7.4.12≥ 8.0.0, < 8.0.12 | 7.4.128.0.12 |
| symfony | ≥ 7.4.0, < 7.4.12≥ 8.0.0, < 8.0.12 | 7.4.128.0.12 |
Symfony's #[IsGranted('...')], #[IsSignatureValid], and #[IsCsrfTokenValid(...)] attributes allow you to define a methods: [...] argument to only enforce these checks for the listed HTTP methods and skip them otherwise. E.g. an attribute defining methods: ['GET'] would be ignored for a HEAD request.
On the other hand, Symfony's router (and HTTP semantics generally) serves HEAD requests using the GET handler. Therefore, a controller protected by e.g. #[IsGranted('ROLE_ADMIN', methods: ['GET'])] can be reached via HEAD with the authorization check silently skipped.
Even if the HEAD request won't get any response content, response headers leak (Content-Length, Location, custom headers). Also, the controller still executes and any side effects (DB writes, state changes) occur.
When adding GET in the methods option of these attributes, Symfony now also include the HEAD method automatically.
The patch for this issue is available here for branch 7.4.
Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and Alexandre Daubois for fixing it.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free