TYPO3 CMS up to 9.5.16/10.4.1 $BE_USER->uc deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TYPO3 CMS up to 9.5.16/10.4.1 and classified as critical. This issue affects some unknown processing. Executing a manipulation of the argument $BE_USER->uc can lead to deserialization. This vulnerability is handled as CVE-2020-11067. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in TYPO3 CMS up to 9.5.16/10.4.1 (Content Management System) and classified as critical. This vulnerability affects an unknown code. The manipulation of the argument $BE_USER->uc with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was released 05/14/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability was named CVE-2020-11067 since 03/30/2020. The attack can be initiated remotely. A single authentication is needed for exploitation. There are known technical details, but no exploit is available.
Upgrading to version 9.5.17 or 10.4.2 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-155235 and VDB-155237. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 9.5.0
- 9.5.1
- 9.5.2
- 9.5.3
- 9.5.4
- 9.5.5
- 9.5.6
- 9.5.7
- 9.5.8
- 9.5.9
- 9.5.10
- 9.5.11
- 9.5.12
- 9.5.13
- 9.5.14
- 9.5.15
- 9.5.16
- 10.4.0
- 10.4.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CMS 9.5.17/10.4.2
Timeline
03/30/2020 🔍05/14/2020 🔍
05/14/2020 🔍
10/18/2020 🔍
Sources
Advisory: github.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-11067 (🔍)
GCVE (CVE): GCVE-0-2020-11067
GCVE (VulDB): GCVE-100-155236
See also: 🔍
Entry
Created: 05/14/2020 16:00Updated: 10/18/2020 07:57
Changes: 05/14/2020 16:00 (40), 05/14/2020 16:05 (12), 10/18/2020 07:51 (1), 10/18/2020 07:57 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.