CVE-2020-11067GHSA-2WJ9-434X-9HVPBIT-TYPO3-2020-11067
Deserialization of Untrusted Data in TYPO3 CMS
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.5.17, 10.4.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- TYPO3 TYPO3 CMS
From 9.0.0 · fixed in 9.5.17; From 10.0.0 · fixed in 10.4.2
- typo3/cms-corePackagist
From 9.0.0 · fixed in 9.5.17
- typo3/cms-corePackagist
From 10.0.0 · fixed in 10.4.2
- typo3/cmsPackagist
From 10.0.0 · fixed in 10.4.2
- typo3/cmsPackagist
From 9.0.0 · fixed in 9.5.17