First published: Fri Mar 15 2024(Updated: )
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 `max_image_size_kb`, `max_attachment_size_kb` and `max_image_megapixels` 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 `max_image_size_kb`, `max_attachment_size_kb` and `max_image_megapixels` as smaller uploads require less resources to process. Alternatively, `client_max_body_size` can be reduced in Nginx to prevent large uploads from reaching the server.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-24827 is considered a medium severity vulnerability due to the potential for DoS attacks from unrestricted uploads.
To fix CVE-2024-24827, implement rate limiting on the POST /uploads endpoint in your Discourse application.
The impact of CVE-2024-24827 includes increased risk of DoS attacks, which can lead to server unavailability.
CVE-2024-24827 affects all versions of Discourse that do not have rate limiting on the POST /uploads endpoint.
CVE-2024-24827 is a vulnerability that can be exploited to launch DoS attacks, affecting the availability of the Discourse application.