CVE-2024-24827: No rate limits on POST /uploads endpoint in Discourse
Discourse is an open source platform for community discussion. Without a rate limit on the POST /uploads endpoint, it makes it easier for an attacker to carry out a DoS attack on the server since creating an upload can be a resource intensive process. Do note that the impact varies from site to site as various site settings like maximagesizekb, maxattachmentsizekb and maximagemegapixels will determine the amount of resources used when creating an upload. The issue is patched in the latest stable, beta and tests-passed version of Discourse. Users are advised to upgrade. Users unable to upgrade should reduce maximagesizekb, maxattachmentsizekb and maximagemegapixels as smaller uploads require less resources to process. Alternatively, clientmaxbodysize can be reduced in Nginx to prevent large uploads from reaching the server.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-24827?
CVE-2024-24827 is considered a medium severity vulnerability due to the potential for DoS attacks from unrestricted uploads.
How do I fix CVE-2024-24827?
To fix CVE-2024-24827, implement rate limiting on the POST /uploads endpoint in your Discourse application.
What impact does CVE-2024-24827 have on my Discourse server?
The impact of CVE-2024-24827 includes increased risk of DoS attacks, which can lead to server unavailability.
Which versions of Discourse are affected by CVE-2024-24827?
CVE-2024-24827 affects all versions of Discourse that do not have rate limiting on the POST /uploads endpoint.
Is CVE-2024-24827 an exploit for Discourse?
CVE-2024-24827 is a vulnerability that can be exploited to launch DoS attacks, affecting the availability of the Discourse application.