Improperly Controlled Modification of Dynamically-Determined Object Attributes 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.17, 10.4.2
- 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.17 and greater than or equal to 10.0.0 and less than 10.4.2, calling unserialize() on malicious user-submitted content can lead to modification of dynamically-determined object attributes and result in triggering deletion of an arbitrary directory in the file system, if it is writable for the web server. It can also trigger message submission via email using the identity of the web site (mail relay). Another insecure deserialization vulnerability is required to actually exploit mentioned aspects. This has been fixed in 9.5.17 and 10.4.2.
Timeline
- CVE published
- Record last updated
Affected versions
- TYPO3 TYPO3 CMS
From 9.0.0 · fixed in 9.5.17; From 10.0.0 · fixed in 10.4.2
- typo3/cms-corePackagist
From 9.0.0 · fixed in 9.5.17
- typo3/cms-corePackagist
From 10.0.0 · fixed in 10.4.2
- typo3/cmsPackagist
From 10.0.0 · fixed in 10.4.2
- typo3/cmsPackagist
From 9.0.0 · fixed in 9.5.17