CVE-2020-11067: Deserialization of Untrusted Data in TYPO3 CMS
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 $BEUSER->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.
Other sources
It has been discovered that backend user settings (in $BEUSER->uc) are vulnerable to insecure deserialization. In combination with vulnerabilities of 3rd party components this can lead to remote code execution. A valid backend user account is needed to exploit this vulnerability.
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-005
— GitHub
TYPO3-CORE-SA-2020-005: Insecure Deserialization in Backend User Settings
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this TYPO3 security advisory?
The vulnerability ID for this TYPO3 security advisory is CVE-2020-11067.
What is the title of this TYPO3 security advisory?
The title of this TYPO3 security advisory is TYPO3-CORE-SA-2020-005: Insecure Deserialization in Backend User Settings.
What is the affected software for this TYPO3 security advisory?
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.
What is the reference for this TYPO3 security advisory?
The reference for this TYPO3 security advisory can be found at https://typo3.org/security/advisory/typo3-core-sa-2020-005.
How can I fix the vulnerability in TYPO3 CMS?
To fix the vulnerability in TYPO3 CMS, you should update to a version that is not affected by the security advisory.