Skip to content

TYPO3 Potential Open Redirect via Parsing Differences

Moderate severity GitHub Reviewed Published Jan 14, 2025 in TYPO3/typo3 • Updated Jan 15, 2025

Package

composer typo3/cms-core (Composer)

Affected versions

>= 9.0.0, <= 9.5.48
>= 10.0.0, <= 10.4.47
>= 11.0.0, <= 11.5.41
>= 12.0.0, <= 12.4.24
>= 13.0.0, <= 13.4.2

Patched versions

9.5.49
10.4.48
11.5.42
12.4.25
13.4.3

Description

Problem

Applications that use TYPO3\CMS\Core\Http\Uri to parse externally provided URLs (e.g., via a query parameter) and validate the host of the parsed URL may be vulnerable to open redirect or SSRF attacks if the URL is used after passing the validation checks.

Solution

Update to TYPO3 versions 9.5.49 ELTS, 10.4.48 ELTS, 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.

Credits

Thanks to Sam Mush and Christian Eßl who reported this issue and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

References

@ohader ohader published to TYPO3/typo3 Jan 14, 2025
Published to the GitHub Advisory Database Jan 14, 2025
Reviewed Jan 14, 2025
Published by the National Vulnerability Database Jan 14, 2025
Last updated Jan 15, 2025

Severity

Moderate

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

EPSS score

0.061%
(28th percentile)

Weaknesses

CVE ID

CVE-2024-55892

GHSA ID

GHSA-2fx5-pggv-6jjr

Source code

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