MediumGHSA-mgj2-q8wp-29rrBIT-typo3-2022-23502CVE-2022-23502

TYPO3 CMS vulnerable to Insufficient Session Expiration after Password Reset

Published 13 Dec 2022 · Updated 6 Dec 2023

Affected packages

typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.33
Fixed in
10.4.33
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.33
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.20
Fixed in
11.5.20
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.20
typo3/cms-coreComposer
Affected
>=12.0.0 <12.1.1
Fixed in
12.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^12.1.1
typo3/cmsComposer
Affected
>=10.0.0 <10.4.33
Fixed in
10.4.33
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.33
typo3/cmsComposer
Affected
>=11.0.0 <11.5.20
Fixed in
11.5.20
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.20
typo3/cmsComposer
Affected
>=12.0.0 <12.1.1
Fixed in
12.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms:^12.1.1

Details

Problem

When users reset their password using the corresponding password recovery functionality, existing sessions for that particular user account were not revoked. This applied to both frontend user sessions and backend user sessions.

Solution

Update to TYPO3 versions 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.

References

Is GHSA-mgj2-q8wp-29rr 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.