CVE-2024-53991: Potential Backup file leaked via Nginx in Discourse
Discourse is an open source platform for community discussion. This vulnerability only impacts Discourse instances configured to use FileStore::LocalStore which means uploads and backups are stored locally on disk. If an attacker knows the name of the Discourse backup file, the attacker can trick nginx into sending the Discourse backup file with a well crafted request. This issue is patched in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. Users unable to upgrade can either 1. Download all local backups on to another storage device, disable the enablebackups site setting and delete all backups until the site has been upgraded to pull in the fix. Or 2. Change the backuplocation site setting to s3 so that backups are stored and downloaded directly from S3.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53991?
CVE-2024-53991 has been rated as a moderate severity vulnerability that can lead to sensitive data exposure.
How do I fix CVE-2024-53991?
To fix CVE-2024-53991, reconfigure your Discourse instance to use an alternative storage backend instead of FileStore::LocalStore.
Which versions of Discourse are affected by CVE-2024-53991?
CVE-2024-53991 affects all versions of Discourse configured to use FileStore::LocalStore on stable, beta, and tests-passed versions.
What types of systems are vulnerable to CVE-2024-53991?
Systems that utilize Discourse with local disk storage for uploads and backups are vulnerable to CVE-2024-53991.
What are the potential impacts of CVE-2024-53991?
The potential impacts of CVE-2024-53991 include unauthorized access to backup files which may contain sensitive data.