title: Cache poisoning via maliciously-formed request in discourse
description: 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.
problem types: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
affected:
{
product: discourse
vendor: discourse
versions:
status: affected, version: < 2.7.10
status: affected, version: >= 2.8.0, < 2.8.0.beta8
}
metrics:
cvssV3_1: [
attackComplexity: HIGH
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 4.8
baseSeverity: MEDIUM
confidentialityImpact: LOW
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
version: 3.1
]