| Package | Affected versions | Patched versions |
|---|---|---|
| typo3/cms | ≥ 10.0.0, < 10.4.32≥ 11.0.0, < 11.5.16 | 10.4.3211.5.16 |
| typo3/cms-core | ≥ 10.0.0, < 10.4.32≥ 11.0.0, < 11.5.16≥ 7.0.0, < 7.6.58≥ 8.0.0, < 8.7.48≥ 9.0.0, < 9.5.37 | 10.4.3211.5.167.6.588.7.489.5.37 |
| typo3 | ≥ 10.0.0, ≤ 10.4.31≥ 11.0.0, ≤ 11.5.15≥ 7.0.0, ≤ 7.6.57≥ 8.0.0, ≤ 8.7.47≥ 9.0.0, ≤ 9.5.36 |
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)
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.
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.
Thanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free