Wagtail up to 5.2.5/6.0.5/6.1.2 parse_query_string redos

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Wagtail up to 5.2.5/6.0.5/6.1.2. Affected by this issue is the function parse_query_string. This manipulation causes redos. This vulnerability is registered as CVE-2024-39317. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Wagtail up to 5.2.5/6.0.5/6.1.2. It has been declared as problematic. Affected by this vulnerability is the function parse_query_string. The manipulation with an unknown input leads to a redos vulnerability. The CWE definition for the vulnerability is CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. As an impact it is known to affect availability. The summary by CVE is:

Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users). Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2024-39317 since 06/21/2024. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1449.003 according to MITRE ATT&CK.

Upgrading to version 5.2.6, 6.0.6 or 6.1.3 eliminates this vulnerability. Applying the patch 31b1e8532dfb1b70d8d37d22aff9cbde9109cdf2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Wagtail

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.1.0
• 6.1.1
• 6.1.2

License

• open-source

Website

• Product: https://github.com/wagtail/wagtail/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion