Authenticated code execution via backend settings deserialization
Published May 13, 2020 · Updated Aug 4, 2024
Insecure deserialization in TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1 allows remote authenticated users to execute code. The backend's unpack_uc method passes the persisted $BE_USER->uc settings blob to PHP unserialize without disabling object instantiation. Exploitation requires a valid backend account and a usable third-party object gadget; successful chaining executes code in the web application context.
Summary
What happened
Insecure deserialization in TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1 allows remote authenticated users to execute code. The backend's unpack_uc method passes the persisted $BE_USER->uc settings blob to PHP unserialize without disabling object instantiation. Exploitation requires a valid backend account and a usable third-party object gadget; successful chaining executes code in the web application context.
The record
- CVE
- CVE-2020-11067
- Published
- May 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- in2code GmbH
- Product
- TYPO3 CMS
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 10.0.0, < 10.4.2
- Affected versionversion=>= 9.0.0, < 9.5.17
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo