TYPO3 Potential Open Redirect via Parsing Differences
Published 14 Jan 2025 · Updated 15 Jan 2025
Affected packages
- Affected
- >=9.0.0 <9.5.49
- Fixed in
- 9.5.49
composer require typo3/cms-core:^9.5.49- Affected
- >=10.0.0 <10.4.48
- Fixed in
- 10.4.48
composer require typo3/cms-core:^10.4.48- Affected
- >=11.0.0 <11.5.42
- Fixed in
- 11.5.42
composer require typo3/cms-core:^11.5.42- Affected
- >=12.0.0 <12.4.25
- Fixed in
- 12.4.25
composer require typo3/cms-core:^12.4.25- Affected
- >=13.0.0 <13.4.3
- Fixed in
- 13.4.3
composer require typo3/cms-core:^13.4.3Details
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
Is GHSA-2fx5-pggv-6jjr in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.