Improperly Controlled Modification of Dynamically-Determined Object Attributes 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.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.
From the CVE record · GitHub_M
TYPO3 CMS can modify object attributes when unserialize() processes malicious user-submitted content. An attacker could delete an arbitrary directory writable by the web server or send email using the website's identity, but exploiting these effects also requires another insecure deserialization vulnerability. The input does not specify whether authentication or user interaction is required.
Operators using Packagist packages typo3/cms-core or typo3/cms in versions >=9.0.0 <9.5.17 or >=10.0.0 <10.4.2 should check their installations.