CVE-2022-31182: Cache poisoning via maliciously-formed request in Discourse
Discourse is the an open source discussion platform. In affected versions a maliciously crafted request for static assets could cause error responses to be cached by Discourse's default NGINX proxy configuration. A corrected NGINX configuration is included in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2022-31182?
CVE-2022-31182 has a severity rating that may vary based on target configuration and environment but is generally considered a medium risk due to potential information leakage.
How do I fix CVE-2022-31182?
To fix CVE-2022-31182, update to the latest stable version of Discourse or modify the NGINX configuration as recommended in the advisory.
Which versions of Discourse are affected by CVE-2022-31182?
CVE-2022-31182 affects Discourse versions prior to 2.8.7 and the 2.9.0-beta7 version.
What vulnerabilities does CVE-2022-31182 introduce?
CVE-2022-31182 can allow a maliciously crafted request for static assets to cause error responses to be cached.
Is there a specific NGINX configuration to correct CVE-2022-31182?
Yes, a corrected NGINX configuration is included in the latest stable release of Discourse to mitigate CVE-2022-31182.