TYPO3s mail‑file spool deserialization flaw lets local users with write access to the spool directory craft a malicious file that is deserialized during the mailer:spool:send command, enabling arbitrary PHP code execution on the web server. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
Weakness
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Typo3 | Typo3 | 10.0.0 (including) | 10.4.55 (excluding) |
| Typo3 | Typo3 | 11.0.0 (including) | 11.5.49 (excluding) |
| Typo3 | Typo3 | 12.0.0 (including) | 12.4.41 (excluding) |
| Typo3 | Typo3 | 13.0.0 (including) | 13.4.23 (excluding) |
| Typo3 | Typo3 | 14.0.0 (including) | 14.0.2 (excluding) |
Potential Mitigations
- Make fields transient to protect them from deserialization.
- An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.