CVE-2024-22188

Problem

Several settings in the Install Tool for configuring the path to system binaries were vulnerable to code execution. Exploiting this vulnerability requires an administrator-level backend user account with system maintainer permissions.

The corresponding change for this advisory involves enforcing the known disadvantages described in TYPO3-PSA-2020-002: Protecting Install Tool with Sudo Mode.

Credits

Thanks to Rickmer Frier & Daniel Jonka who reported this issue and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

• TYPO3-CORE-SA-2024-002

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2024-22188 has a CVSS score of 7.2 (High). The vector is network-reachable, high 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 (8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.

1. What is CVE-2024-22188? CVE-2024-22188 is a high-severity command injection vulnerability in typo3/cms-core (composer), affecting versions >= 8.0.0, <= 8.7.56. It is fixed in 8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is CVE-2024-22188? CVE-2024-22188 has a CVSS score of 7.2 (High). 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 versions of typo3/cms-core are affected by CVE-2024-22188? typo3/cms-core (composer) versions >= 8.0.0, <= 8.7.56 is affected.
4. Is there a fix for CVE-2024-22188? Yes. CVE-2024-22188 is fixed in 8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1. Upgrade to this version or later.
5. Is CVE-2024-22188 exploitable, and should I be worried? Whether CVE-2024-22188 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-2024-22188 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-2024-22188?
   • Upgrade typo3/cms-core to 8.7.57 or later
   • Upgrade typo3/cms-core to 9.5.46 or later
   • Upgrade typo3/cms-core to 10.4.43 or later
   • Upgrade typo3/cms-core to 11.5.35 or later
   • Upgrade typo3/cms-core to 12.4.11 or later
   • Upgrade typo3/cms-core to 13.0.1 or later