Deserialization of untrusted data in Symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/cache Packagist |
|
|
| symfony/phpunit-bridge Packagist |
| Product | Affected | Fixed in |
|---|---|---|
| symfony/cache Packagist |
|
|
| symfony/phpunit-bridge Packagist |
≥ 2.8.0 · < 2.8.50≥ 3.0.0 · < 3.4.26≥ 4.0.0 · < 4.1.12≥ 4.2.0 · < 4.2.7
|
| symfony/symfony Packagist |
|
|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
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.
From the CVE record · mitre
Symfony can cache objects containing bad user input. Serializing or unserializing those objects could delete files accessible to the current user. The input does not specify whether an attacker needs network access, authentication, or user interaction.
Check installations of symfony/cache, symfony/phpunit-bridge, or symfony/symfony below their listed fixed versions, and typo3/cms-core or typo3/cms versions 9.0.0 through 9.5.7.