| Package | Affected versions | Patched versions |
|---|---|---|
| symfony/cache | ≥ 3.1.0, < 3.4.26≥ 4.0.0, < 4.1.12≥ 4.2.0, < 4.2.7 | 3.4.264.1.124.2.7 |
| symfony/phpunit-bridge | ≥ 2.8.0, < 2.8.50≥ 3.0.0, < 3.4.26≥ 4.0.0, < 4.1.12≥ 4.2.0, < 4.2.7 | 2.8.503.4.264.1.124.2.7 |
| symfony/symfony | ≥ 2.8.0, < 2.8.50≥ 3.0.0, < 3.4.26≥ 4.0.0, < 4.1.12≥ 4.2.0, < 4.2.7 | 2.8.503.4.264.1.124.2.7 |
| typo3/cms | ≥ 9.0.0, < 9.5.8 | 9.5.8 |
| typo3/cms-core | ≥ 9.0.0, < 9.5.8 | 9.5.8 |
| symfony | ≥ 2.8.0, < 2.8.50≥ 3.4.0, < 3.4.26≥ 4.1.0, < 4.1.12≥ 4.2.0, < 4.2.7 | 2.8.503.4.264.1.124.2.7 |
In Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free