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.

Vulnerability/
CVE-2022-31182

medium

5.3

CWE

404

1/8/2022

3/8/2024

CVE-2022-31182: Cache poisoning via maliciously-formed request in Discourse

First published: Mon Aug 01 2022(Updated: )

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.

Credit: security-advisories@github.com

Affected Software	Affected Version	How to fix
Discourse	<2.8.7
Discourse	=2.9.0-beta7

Remedy

https://github.com/discourse/discourse/commit/7af25544c3940c4d046c51f4cfac9c72a06d4f50

Never miss a vulnerability like this again

Reference Links

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.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/last-modified-date
agent/severity
agent/remedy
agent/title
agent/weakness
agent/first-publish-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/discourse
canonical/discourse
version/discourse/2.9.0-beta7

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.