CVE-2022-36105

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.

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)

CVE-2022-36105 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2022-36105? CVE-2022-36105 is a medium-severity security vulnerability in typo3/cms-core (composer), affecting versions >= 7.0.0, < 7.6.58. It is fixed in 7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16.
2. How severe is CVE-2022-36105? CVE-2022-36105 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-36105?
   • typo3/cms-core (composer) (versions >= 7.0.0, < 7.6.58)
   • typo3/cms (composer) (versions >= 10.0.0, < 10.4.32)
4. Is there a fix for CVE-2022-36105? Yes. CVE-2022-36105 is fixed in 7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16. Upgrade to this version or later.
5. Is CVE-2022-36105 exploitable, and should I be worried? Whether CVE-2022-36105 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-36105 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-36105?
   • Upgrade typo3/cms-core to 7.6.58 or later
   • Upgrade typo3/cms-core to 8.7.48 or later
   • Upgrade typo3/cms-core to 9.5.37 or later
   • Upgrade typo3/cms-core to 10.4.32 or later
   • Upgrade typo3/cms-core to 11.5.16 or later
   • Upgrade typo3/cms to 10.4.32 or later
   • Upgrade typo3/cms to 11.5.16 or later