Missing Required Cryptographic Step Leading to Sensitive Information Disclosure 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.20, 10.4.6
- 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 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.
Timeline
- CVE published
- Record last updated
Affected versions
- TYPO3 TYPO3 CMS
From 9.0.0 · fixed in 9.5.20
- typo3/cms-corePackagist
From 9.0.0 · fixed in 9.5.20
- typo3/cms-corePackagist
From 10.0.0 · fixed in 10.4.6
- typo3/cmsPackagist
From 10.0.0 · fixed in 10.4.6
- typo3/cmsPackagist
From 9.0.0 · fixed in 9.5.20