First published: Tue May 12 2020(Updated: )
In TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of third party components, this can lead to remote code execution. A valid backend user account is needed to exploit this vulnerability. This has been fixed in 9.5.17 and 10.4.2.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/typo3/cms | >=10.0.0<10.4.2>=9.0.0<9.5.17 | |
composer/typo3/cms-core | >=10.0.0<10.4.2>=9.0.0<9.5.17 | |
Typo3 Typo3 | >=9.0.0<=9.5.16 | |
Typo3 Typo3 | >=10.0.0<=10.4.1 | |
composer/typo3/cms | >=9.0.0<9.5.17 | 9.5.17 |
composer/typo3/cms | >=10.0.0<10.4.2 | 10.4.2 |
composer/typo3/cms-core | >=10.0.0<10.4.2 | 10.4.2 |
composer/typo3/cms-core | >=9.0.0<9.5.17 | 9.5.17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this TYPO3 security advisory is CVE-2020-11067.
The title of this TYPO3 security advisory is TYPO3-CORE-SA-2020-005: Insecure Deserialization in Backend User Settings.
The affected software for this TYPO3 security advisory is TYPO3 CMS versions 9.0.0 to 9.5.17 and 10.0.0 to 10.4.2.
The reference for this TYPO3 security advisory can be found at https://typo3.org/security/advisory/typo3-core-sa-2020-005.
To fix the vulnerability in TYPO3 CMS, you should update to a version that is not affected by the security advisory.