Discourse is an open source discussion platform. Discourse groups can be configured with varying visibility levels for the group as well as the group members. By default, a newly created group has its visibility set to public and the groups members visibility set to public as well. However, a groups visibility and the groups members visibility can be configured such that it is restricted to logged on users, members of the group or staff users. A vulnerability has been discovered in versions prior to 2.7.13 and 2.8.0.beta11 where the group advanced search option does not respect the groups visibility and members visibility level. As such, a group with restricted visibility or members visibility can be revealed through search with the right search option. This issue is patched in stable
version 2.7.13, beta
version 2.8.0.beta11, and tests-passed
version 2.8.0.beta11 versions of Discourse. There are no workarounds aside from upgrading.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Discourse | Discourse | * | 2.7.12 (including) |
Discourse | Discourse | 2.8.0-beta1 (including) | 2.8.0-beta1 (including) |
Discourse | Discourse | 2.8.0-beta10 (including) | 2.8.0-beta10 (including) |
Discourse | Discourse | 2.8.0-beta2 (including) | 2.8.0-beta2 (including) |
Discourse | Discourse | 2.8.0-beta3 (including) | 2.8.0-beta3 (including) |
Discourse | Discourse | 2.8.0-beta4 (including) | 2.8.0-beta4 (including) |
Discourse | Discourse | 2.8.0-beta5 (including) | 2.8.0-beta5 (including) |
Discourse | Discourse | 2.8.0-beta6 (including) | 2.8.0-beta6 (including) |
Discourse | Discourse | 2.8.0-beta7 (including) | 2.8.0-beta7 (including) |
Discourse | Discourse | 2.8.0-beta8 (including) | 2.8.0-beta8 (including) |
Discourse | Discourse | 2.8.0-beta9 (including) | 2.8.0-beta9 (including) |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.