Skip to content

Class destructors causing side-effects when being unserialized in TYPO3 CMS

High severity GitHub Reviewed Published May 12, 2020 in TYPO3/typo3 • Updated Feb 7, 2024

Package

composer typo3/cms (Composer)

Affected versions

>= 10.0.0, < 10.4.2
>= 9.0.0, < 9.5.17

Patched versions

10.4.2
9.5.17
composer typo3/cms-core (Composer)
>= 9.0.0, < 9.5.17
>= 10.0.0, < 10.4.2
9.5.17
10.4.2

Description

Calling unserialize() on malicious user-submitted content can result in the following scenarios:

  • trigger deletion of arbitrary directory in file system (if writable for web server)
  • trigger message submission via email using identity of web site (mail relay)

Another insecure deserialization vulnerability is required to actually exploit mentioned aspects.

Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.

References

References

@ohader ohader published to TYPO3/typo3 May 12, 2020
Reviewed May 13, 2020
Published to the GitHub Advisory Database May 13, 2020
Published by the National Vulnerability Database May 14, 2020
Last updated Feb 7, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(66th percentile)

Weaknesses

Improperly Controlled Modification of Dynamically-Determined Object Attributes

The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. Learn more on MITRE.

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. Learn more on MITRE.

CVE ID

CVE-2020-11066

GHSA ID

GHSA-2rxh-h6h9-qrqc

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.