Skip to content

TYPO3 CMS vulnerable to User Enumeration via Response Timing

Moderate severity GitHub Reviewed Published Sep 13, 2022 in TYPO3/typo3 • Updated Jan 27, 2023

Package

composer typo3/cms (Composer)

Affected versions

>= 10.0.0, < 10.4.32
>= 11.0.0, < 11.5.16

Patched versions

10.4.32
11.5.16
composer typo3/cms-core (Composer)
>= 7.0.0, < 7.6.58
>= 8.0.0, < 8.7.48
>= 9.0.0, < 9.5.37
>= 10.0.0, < 10.4.32
>= 11.0.0, < 11.5.16
7.6.58
8.7.48
9.5.37
10.4.32
11.5.16

Description

Meta

  • CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C (4.9)

Problem

It has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.

Extension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new MimicServiceInterface::mimicAuthUser, which simulates corresponding times regular processing would usually take.

Solution

Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.

Credits

Thanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.

References

References

@ohader ohader published to TYPO3/typo3 Sep 13, 2022
Published by the National Vulnerability Database Sep 13, 2022
Published to the GitHub Advisory Database Sep 16, 2022
Reviewed Sep 16, 2022
Last updated Jan 27, 2023

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

EPSS score

0.071%
(33rd percentile)

Weaknesses

CVE ID

CVE-2022-36105

GHSA ID

GHSA-m392-235j-9r7r

Source code

Credits

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