Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS
TYPO3 CMS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
TYPO3 CMS
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.20, and greater than or equal to 10.0.0 and less than 10.4.6, it has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains including potential privilege escalation, insecure deserialization & remote code execution. The overall severity of this vulnerability is high based on mentioned attack chains and the requirement of having a valid backend user session (authenticated). This has been patched in versions 9.5.20 and 10.4.6.
From the CVE record · GitHub_M
An internal verification mechanism in TYPO3 CMS can generate arbitrary checksums, allowing an attacker to inject data with a valid HMAC-SHA1 code. With a valid authenticated backend user session, this can enable attack chains including potential privilege escalation, insecure deserialization, and remote code execution.
Anyone running TYPO3 CMS or the Packagist packages typo3/cms-core or typo3/cms at versions >=9.0.0 and <9.5.20, or >=10.0.0 and <10.4.6, should check their installation.