Skip to content

XML External Entity in Dashboard Widget

Low severity GitHub Reviewed Published Nov 17, 2020 in TYPO3/typo3 • Updated Feb 15, 2024

Package

composer typo3/cms (Composer)

Affected versions

>= 10.0.0, < 10.4.10

Patched versions

10.4.10
composer typo3/cms-core (Composer)
>= 10.0.0, < 10.4.10
10.4.10

Description

Problem

It has been discovered that RSS widgets are susceptible to XML external entity processing.
This vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions.

At least with libxml2 version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed.

Solution

Update to TYPO3 version 10.4.10 that fixes the problem described.

References

@ohader ohader published to TYPO3/typo3 Nov 17, 2020
Reviewed Nov 23, 2020
Published to the GitHub Advisory Database Nov 23, 2020
Published by the National Vulnerability Database Nov 23, 2020
Last updated Feb 15, 2024

Severity

Low

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

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:L/UI:R/S:U/C:L/I:N/A:L

EPSS score

0.072%
(32nd percentile)

Weaknesses

CVE ID

CVE-2020-26229

GHSA ID

GHSA-q9cp-mc96-m4w2

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.