MediumGHSA-5959-4x58-r8c2BIT-typo3-2022-36106CVE-2022-36106

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

Published 16 Sept 2022 · Updated 6 Dec 2023

Affected packages

typo3/cms-coreComposer
Affected
>=10.4.0 <10.4.32
Fixed in
10.4.32
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.32
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.16
Fixed in
11.5.16
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.16
typo3/cmsComposer
Affected
>=10.4.0 <10.4.32
Fixed in
10.4.32
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.32
typo3/cmsComposer
Affected
>=11.0.0 <11.5.16
Fixed in
11.5.16
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.16

Details

> ### 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

Is GHSA-5959-4x58-r8c2 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.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.