CVE-2022-36105: TYPO3 CMS vulnerable to User Enumeration via Response Timing
5.3
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.61959%
CWE
Published
9/16/2022
Updated
1/27/2023
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| typo3/cms-core | composer | >= 7.0.0, < 7.6.58 | 7.6.58 |
| typo3/cms-core | composer | >= 8.0.0, < 8.7.48 | 8.7.48 |
| typo3/cms-core | composer | >= 9.0.0, < 9.5.37 | 9.5.37 |
| typo3/cms-core | composer | >= 10.0.0, < 10.4.32 | 10.4.32 |
| typo3/cms-core | composer | >= 11.0.0, < 11.5.16 | 11.5.16 |
| typo3/cms | composer | >= 10.0.0, < 10.4.32 | 10.4.32 |
| typo3/cms | composer | >= 11.0.0, < 11.5.16 | 11.5.16 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from timing discrepancies during authentication. The checkAuthentication method controlled the authentication flow but lacked code to simulate delays for invalid users, making response times leak user existence. The authUser method's password validation for valid users created a baseline timing difference. The fix introduced mimicAuthUser in AuthenticationService and triggered it in checkAuthentication to eliminate this discrepancy. Third-party authentication services without mimicAuthUser implementations would also be vulnerable, but the core issue resides in the unpatched checkAuthentication flow and authUser's lack of mitigation.