~ / search / GHSA-m392-235j-9r7r

GHSA-m392-235j-9r7r

TYPO3 CMS vulnerable to User Enumeration via Response Timing

Source: GitHub Advisory Database (reviewed) Moderate CVE-2022-36105

Packages

EcosystemPackageAffectedFixed in
Packagist typo3/cms-core >= 7.0.0, < 7.6.58 7.6.58
Packagist typo3/cms-core >= 8.0.0, < 8.7.48 8.7.48
Packagist typo3/cms-core >= 9.0.0, < 9.5.37 9.5.37
Packagist typo3/cms-core >= 10.0.0, < 10.4.32 10.4.32
Packagist typo3/cms-core >= 11.0.0, < 11.5.16 11.5.16
Packagist typo3/cms >= 10.0.0, < 10.4.32 10.4.32
Packagist typo3/cms >= 11.0.0, < 11.5.16 11.5.16

Details

As written in the advisory (Markdown source, shown as plain text).

> ### 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 * [TYPO3-CORE-SA-2022-007](https://typo3.org/security/advisory/typo3-core-sa-2022-007) * [Vulnerability Report on huntr.dev](https://huntr.dev/bounties/7d519735-2877-4fad-bd77-accde3e290a7/) (embargoed +30 days)

References

External links from the advisory. They lead to third-party sites.