CVE-2022-24800

Workarounds

Apply https://github.com/octobercms/library/commit/fe569f3babf3f593be2b1e0a4ae0283506127a83 to your installation manually if unable to upgrade to Build 476 (v1.0.476) or v1.1.12 or v2.2.15.

References

Credits to:

• DucNT, HungTD and GiangVQ from RedTeam@VNG Security Response Center.

For more information

If you have any questions or comments about this advisory:

• Email us at [email protected]

This advisory affects plugins that expose the October\Rain\Database\Attach\File::fromData as a public interface. This vulnerability does not affect vanilla installations of October CMS since this method is not exposed or used by the system internally or externally.

When the developer allows the user to specify their own filename in the fromData method, an unauthenticated user can perform remote code execution (RCE) by exploiting a race condition in the temporary storage directory.

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2022-24800 has a CVSS score of 8.1 (High). 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 (1.0.476, 1.1.12, 2.2.15); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been patched in Build 476 (v1.0.476) and v1.1.12 and v2.2.15.

1. What is CVE-2022-24800? CVE-2022-24800 is a high-severity race condition vulnerability in october/system (composer), affecting versions < 1.0.476. It is fixed in 1.0.476, 1.1.12, 2.2.15. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
2. How severe is CVE-2022-24800? CVE-2022-24800 has a CVSS score of 8.1 (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 october/system are affected by CVE-2022-24800? october/system (composer) versions < 1.0.476 is affected.
4. Is there a fix for CVE-2022-24800? Yes. CVE-2022-24800 is fixed in 1.0.476, 1.1.12, 2.2.15. Upgrade to this version or later.
5. Is CVE-2022-24800 exploitable, and should I be worried? Whether CVE-2022-24800 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-24800 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-24800?
   • Upgrade october/system to 1.0.476 or later
   • Upgrade october/system to 1.1.12 or later
   • Upgrade october/system to 2.2.15 or later