Skip to content

TYPO3 Backend Forms vulnerable to Information Disclosure of Hashed Passwords

Moderate severity GitHub Reviewed Published Feb 13, 2024 in TYPO3/typo3 • Updated Feb 14, 2024

Package

composer typo3/cms-core (Composer)

Affected versions

>= 8.0.0, <= 8.7.56
>= 9.0.0, <= 9.5.45
>= 10.0.0, <= 10.4.42
>= 11.0.0, <= 11.5.34
>= 12.0.0, <= 12.4.10
= 13.0.0

Patched versions

8.7.57
9.5.46
10.4.43
11.5.35
12.4.11
13.0.1

Description

Problem

Password hashes were being reflected in the editing forms of the TYPO3 backend user interface. This allowed attackers to crack the plaintext password using brute force techniques. Exploiting this vulnerability requires a valid backend user account.

Solution

Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.

Credits

Thanks to the TYPO3 framework merger Christian Kuhn and external security researchers Maximilian Beckmann, Klaus-Günther Schmidt who reported this issue, and TYPO3 security team member Oliver Hader who fixed the issue.

References

References

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

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
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.049%
(19th percentile)

Weaknesses

CVE ID

CVE-2024-25118

GHSA ID

GHSA-38r2-5695-334w

Source code

Credits

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