GHSA-2rxh-h6h9-qrqc
Class destructors causing side-effects when being unserialized in TYPO3 CMS
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Packagist | typo3/cms-core | >= 9.0.0, < 9.5.17 | 9.5.17 |
| Packagist | typo3/cms-core | >= 10.0.0, < 10.4.2 | 10.4.2 |
| Packagist | typo3/cms | >= 10.0.0, < 10.4.2 | 10.4.2 |
| Packagist | typo3/cms | >= 9.0.0, < 9.5.17 | 9.5.17 |
Details
As written in the advisory (Markdown source, shown as plain text).
Calling unserialize() on malicious user-submitted content can result in the following scenarios:
- trigger deletion of arbitrary directory in file system (if writable for web server)
- trigger message submission via email using identity of web site (mail relay)
Another insecure deserialization vulnerability is required to actually exploit mentioned aspects.
Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.
### References
* https://typo3.org/security/advisory/typo3-core-sa-2020-004
References
External links from the advisory. They lead to third-party sites.
- https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-2rxh-h6h9-qrqc
- https://nvd.nist.gov/vuln/detail/CVE-2020-11066
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-11066.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-11066.yaml
- https://typo3.org/security/advisory/typo3-core-sa-2020-004