Skip to content

User's read state for a topic is leaked when unread state message is published from the server to the clients.

Moderate
tgxworld published GHSA-gq2h-qhg2-phf9 Aug 13, 2021

Package

Discourse

Affected versions

stable <= 2.7.7; beta <= 2.8.0.beta4; tests-passed <= 2.8.0.beta4

Patched versions

stable <= 2.7.8; beta <= 2.8.0.beta5; tests-passed <= 2.8.0.beta5

Description

Impact

A user's read state for a topic such as the last read post number and the notification level is exposed.

Patches

This issue is patched in the latest stable, beta and tests-passed versions of Discourse.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

CVE ID

CVE-2021-37703

Weaknesses