CVE-2022-36106

Meta

• CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N/E:F/RL:O/RC:C (5.0)

Problem

It has been discovered that the expiration time of a password reset link for TYPO3 backend users has never been evaluated. As a result, a password reset link could be used to perform a password reset even if the default expiry time of two hours has been exceeded.

Credits

Thanks to Ingo Fabbri who reported this issue and to TYPO3 security team member Torben Hansen who fixed the issue.

References

• TYPO3-CORE-SA-2022-008

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2022-36106 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low 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 (10.4.32, 11.5.16); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 version 10.4.32 or 11.5.16 that fix the problem described above.

1. What is CVE-2022-36106? CVE-2022-36106 is a medium-severity improper authentication vulnerability in typo3/cms-core (composer), affecting versions >= 10.4.0, < 10.4.32. It is fixed in 10.4.32, 11.5.16. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2022-36106? CVE-2022-36106 has a CVSS score of 5.4 (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-36106?
   • typo3/cms-core (composer) (versions >= 10.4.0, < 10.4.32)
   • typo3/cms (composer) (versions >= 10.4.0, < 10.4.32)
4. Is there a fix for CVE-2022-36106? Yes. CVE-2022-36106 is fixed in 10.4.32, 11.5.16. Upgrade to this version or later.
5. Is CVE-2022-36106 exploitable, and should I be worried? Whether CVE-2022-36106 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-36106 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-36106?
   • 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