TYPO3-CORE-SA-2020-004: Class destructors causing side-effects when being unserialized

Problem Description

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.

Solution

Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.

Credits

Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.

General Advice

Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list.

General Note

All security related code changes are tagged so that you can easily look them up in our review system.

Zurück