Discourse: Presence of read restricted topics may be leaked if tagged with a tag that is visible to all users
Vulnerability Description
Discourse is an open-source discussion platform. Prior to version 3.0.1 of the `stable` branch and version 3.1.0.beta2 of the `beta` and `tests-passed` branches, the count of topics displayed for a tag is a count of all regular topics regardless of whether the topic is in a read restricted category or not. As a result, any users can technically poll a sensitive tag to determine if a new topic is created in a category which the user does not have excess to. In version 3.0.1 of the `stable` branch and version 3.1.0.beta2 of the `beta` and `tests-passed` branches, the count of topics displayed for a tag defaults to only counting regular topics which are not in read restricted categories. Staff users will continue to see a count of all topics regardless of the topic's category read restrictions.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2023-23622
Credits & Attribution
No credits recorded in the NVD database.
References
- https://github.com/discourse/discourse/security/advisories/GHSA-2wvr-4x7w-v795
- https://github.com/discourse/discourse/pull/20004
- https://github.com/discourse/discourse/pull/20005
- https://github.com/discourse/discourse/commit/105fee978d73b0ec23ff814a09d1c0c9ace95164
- https://github.com/discourse/discourse/commit/ecb9aa5dba94741d9579f4f873f0675f48b4184f
More from discourse
View All →Affected Vendor
discourse
View all reports →