Winter 1.1.8/1.1.9/1.2.0 Snowboard Framework prototype pollution

Summaryinfo

A vulnerability described as critical has been identified in Winter 1.1.8/1.1.9/1.2.0. This affects an unknown function of the component Snowboard Framework. Executing a manipulation can lead to prototype pollution. This vulnerability appears as CVE-2022-39357. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability was found in Winter 1.1.8/1.1.9/1.2.0. It has been declared as critical. This vulnerability affects an unknown code block of the component Snowboard Framework. The manipulation with an unknown input leads to a prototype pollution vulnerability. The CWE definition for the vulnerability is CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Winter is a free, open-source content management system based on the Laravel PHP framework. The Snowboard framework in versions 1.1.8, 1.1.9, and 1.2.0 is vulnerable to prototype pollution in the main Snowboard class as well as its plugin loader. The 1.0 branch of Winter is not affected, as it does not contain the Snowboard framework. This issue has been patched in v1.1.10 and v1.2.1. As a workaround, one may avoid this issue by following some common security practices for JavaScript, including implementing a content security policy and auditing scripts.

The weakness was presented 10/26/2022 as GHSA-3fh5-q6fg-w28q. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-39357 since 09/02/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.

Upgrading to version 1.1.10 or 1.2.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 2a13faf99972e84c9661258f16c4750fa99d29a1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be patching the affected component.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Winter

Version

• 1.1.8
• 1.1.9
• 1.2.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion