CVE-2021-41271: Cache poisoning via maliciously-formed request in discourse

First published: Mon Nov 15 2021(Updated: )

Discourse is a platform for community discussion. In affected versions a maliciously crafted request could cause an error response to be cached by intermediate proxies. This could cause a loss of confidentiality for some content. This issue is patched in the latest stable, beta and tests-passed versions of Discourse.

Credit: security-advisories@github.com security-advisories@github.com

Affected Software	Affected Version	How to fix
Discourse Discourse	<=2.7.9
Discourse Discourse	=2.8.0-beta1
Discourse Discourse	=2.8.0-beta2
Discourse Discourse	=2.8.0-beta3
Discourse Discourse	=2.8.0-beta4
Discourse Discourse	=2.8.0-beta5
Discourse Discourse	=2.8.0-beta6
Discourse Discourse	=2.8.0-beta7
	<=2.7.9
	=2.8.0-beta1
	=2.8.0-beta2
	=2.8.0-beta3
	=2.8.0-beta4
	=2.8.0-beta5
	=2.8.0-beta6
	=2.8.0-beta7

Remedy

https://github.com/discourse/discourse/commit/2da0001965c6d8632d723c46ea5df9f22a1a23f1

Never miss a vulnerability like this again

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.