GitHub Advisoryadvisory · Packagist

GHSA-m392-235j-9r7r TYPO3 CMS vulnerable to User Enumeration via Response Timing

MEDIUM Published 2022-09-16 Modified 2022-09-16 Official page ↗
Aliases
CVE-2022-36105
Ecosystem
Packagist
Packages
typo3/cms-core, typo3/cms
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-203
Reviewed
2022-09-16

Affected packages

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

Description

> ### 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 • Vulnerability Report on huntr.dev (embargoed +30 days)

Related

Alias · CVE (1)

  • CVE-2022-36105 TYPO3 is an open source PHP based web content management system released under the GNU GPL. vulnerability

Weakness · CWE (1)

  • CWE-203 Observable Discrepancy weakness

References