Discourse is the an open source discussion platform. In some rare cases users redeeming an invitation can be added as a participant to several private message topics that they should not be added to. They are not notified of this, it happens transparently in the background. This issue has been resolved in commit a414520742 and will be included in future releases. Users are advised to upgrade. Users are also advised to set SiteSetting.max_invites_per_day to 0 until the patch is installed.
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.8.10 (excluding) |
| Discourse | Discourse | 2.9.0-beta1 (including) | 2.9.0-beta1 (including) |
| Discourse | Discourse | 2.9.0-beta10 (including) | 2.9.0-beta10 (including) |
| Discourse | Discourse | 2.9.0-beta2 (including) | 2.9.0-beta2 (including) |
| Discourse | Discourse | 2.9.0-beta3 (including) | 2.9.0-beta3 (including) |
| Discourse | Discourse | 2.9.0-beta4 (including) | 2.9.0-beta4 (including) |
| Discourse | Discourse | 2.9.0-beta5 (including) | 2.9.0-beta5 (including) |
| Discourse | Discourse | 2.9.0-beta6 (including) | 2.9.0-beta6 (including) |
| Discourse | Discourse | 2.9.0-beta7 (including) | 2.9.0-beta7 (including) |
| Discourse | Discourse | 2.9.0-beta8 (including) | 2.9.0-beta8 (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.