CVE-2024-37299 Discourse vulnerable to DoS via Tag Group
Attackers can cause denial of service by submitting excessively long tag group names, affecting Discourse forum availability.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-37299?
CVE-2024-37299 is a medium-severity denial of service vulnerability in Discourse Discourse, published on 30 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Discourse is an open source discussion platform. Prior to 3.2.5 and 3.3.0.beta5, crafting requests to submit very long tag group names can reduce the availability of a Discourse instance. This vulnerability is fixed in 3.2.5 and 3.3.0.beta5.
Weakness: CWE-400
Which versions are affected by CVE-2024-37299?
1 open source package ship an affected version, including discourse. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
discourse Bitnami | All versions | 3.2.5 |
Products include Discourse Discourse.
How do I fix CVE-2024-37299?
Upgrade discourse to 3.2.5 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2024-37299 being exploited?
There is no known exploitation of CVE-2024-37299 in the wild and no public exploit code.
Other vulnerabilities in Discourse Discourse
- CVE-2021-41163 RCE via malicious SNS subscription payload
- CVE-2022-36066 Discourse vulnerable to RCE via admins uploading maliciously zipped file
- CVE-2022-39356 Discourse user account takeover via email and invite link
- CVE-2023-22468 Discourse vulnerable to Cross-site Scripting in local oneboxes
- CVE-2026-27934 Discourse leaks private topic title and post excerpt via user action API endpoint
Sources
Also known as BIT-discourse-2024-37299, GHSA-4j6h-9pjp-5476.