Описание
Class destructors causing side-effects when being unserialized in TYPO3 CMS
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://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
Пакеты
typo3/cms-core
>= 9.0.0, < 9.5.17
9.5.17
typo3/cms-core
>= 10.0.0, < 10.4.2
10.4.2
typo3/cms
>= 10.0.0, < 10.4.2
10.4.2
typo3/cms
>= 9.0.0, < 9.5.17
9.5.17
Связанные уязвимости
In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, calling unserialize() on malicious user-submitted content can lead to modification of dynamically-determined object attributes and result in triggering deletion of an arbitrary directory in the file system, if it is writable for the web server. It can also trigger message submission via email using the identity of the web site (mail relay). Another insecure deserialization vulnerability is required to actually exploit mentioned aspects. This has been fixed in 9.5.17 and 10.4.2.