Deserialization in TYPO3
CVE-2020-11067
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.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.020 (80.5th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 80th percentile — 80.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.020 · newest: 0.020 · change: 0.000
Affected products
Weakness classification (CWE)
References
- github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-2wj9-434x-9hvp (Third Party Advisory)
Frequently asked questions
- What is CVE-2020-11067?
- CVE-2020-11067 is a high-severity vulnerability in TYPO3, classified under Deserialization of Untrusted Data. CVSS score: 8.8/10. Published 2020-05-14.
- How severe is CVE-2020-11067?
- High severity. CVSS v3 base score is 8.8 out of 10.