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.
This vulnerability affects all unpatched versions from Wagtail 2.0 onwards.
Site owners who are unable to upgrade to a patched version can limit the length of search terms passed to parse_query_string
. Whilst the performance characteristics will depend on your hosting environment, 1000 characters has been shown to still be fairly fast, without triggering this vulnerability.
No workaround is available for the Wagtail admin usage.
Many thanks to Jake Howard for reporting this issue.
If you have any questions or comments about this advisory:
{ "nvd_published_at": "2024-07-11T16:15:02Z", "cwe_ids": [ "CWE-1333" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-07-11T13:21:42Z" }