CVE-2022-39357

Prototype pollution in Snowboard framework

Workarounds

If you have not yet upgraded, or are using the 1.1 branch of Winter (1.1.8 or above), you can avoid this issue by following some common security practices for JavaScript, including implementing a content security policy and auditing your scripts.

The 1.0 branch of Winter is not affected, as it does not contain the Snowboard framework.

For more information

If you have any questions or comments about this advisory:

• Email us at [email protected]

The Snowboard framework in affected versions is vulnerable to prototype pollution in the main Snowboard class as well as its plugin loader.

CVE-2022-39357 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.1.10, 1.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This issue has been patched in https://github.com/wintercms/winter/commit/2a13faf99972e84c9661258f16c4750fa99d29a1 (for 1.2) and https://github.com/wintercms/winter/commit/bce4b59584abf961e9400af3d7a4fd7638e26c7f (for 1.1) and is available with Winter v1.1.10 and v1.2.1.

1. What is CVE-2022-39357? CVE-2022-39357 is a high-severity security vulnerability in wintercms/winter (composer), affecting versions >= 1.1.8, < 1.1.10. It is fixed in 1.1.10, 1.2.1.
2. How severe is CVE-2022-39357? CVE-2022-39357 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 wintercms/winter are affected by CVE-2022-39357? wintercms/winter (composer) versions >= 1.1.8, < 1.1.10 is affected.
4. Is there a fix for CVE-2022-39357? Yes. CVE-2022-39357 is fixed in 1.1.10, 1.2.1. Upgrade to this version or later.
5. Is CVE-2022-39357 exploitable, and should I be worried? Whether CVE-2022-39357 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-39357 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-39357?
   • Upgrade wintercms/winter to 1.1.10 or later
   • Upgrade wintercms/winter to 1.2.1 or later

Other vulnerabilities in wintercms/winter