Skip to content

TYPO3 CMS missing check for expiration time of password reset token for backend users

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

Package

composer typo3/cms (Composer)

Affected versions

>= 10.4.0, < 10.4.32
>= 11.0.0, < 11.5.16

Patched versions

10.4.32
11.5.16
composer typo3/cms-core (Composer)
>= 10.4.0, < 10.4.32
>= 11.0.0, < 11.5.16
10.4.32
11.5.16

Description

Meta

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

Problem

It has been discovered that the expiration time of a password reset link for TYPO3 backend users has never been evaluated. As a result, a password reset link could be used to perform a password reset even if the default expiry time of two hours has been exceeded.

Solution

Update to TYPO3 version 10.4.32 or 11.5.16 that fix the problem described above.

Credits

Thanks to Ingo Fabbri who reported this issue and to TYPO3 security team member Torben Hansen 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
Low
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:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.059%
(26th percentile)

Weaknesses

CVE ID

CVE-2022-36106

GHSA ID

GHSA-5959-4x58-r8c2

Source code

Credits

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