First published: Mon Jun 27 2022(Updated: )
Discourse is an open source discussion platform. Under certain conditions, a logged in user can redeem an invite with an email that either doesn't match the invite's email or does not adhere to the email domain restriction of an invite link. The impact of this flaw is aggravated when the invite has been configured to add the user that accepts the invite into restricted groups. Once a user has been incorrectly added to a restricted group, the user may then be able to view content which that are restricted to the respective group. Users are advised to upgrade to the current stable releases. There are no known workarounds to this issue.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse | <=2.8.4 | |
Discourse | =2.9.0-beta1 | |
Discourse | =2.9.0-beta2 | |
Discourse | =2.9.0-beta3 | |
Discourse | =2.9.0-beta4 | |
Discourse | =2.9.0-beta5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-31096 has a moderate severity rating due to improper handling of invite link restrictions.
To fix CVE-2022-31096, update Discourse to a version beyond 2.8.4 or a stable release after 2.9.0-beta5.
CVE-2022-31096 affects logged-in users of Discourse who may redeem invites without proper email verification.
The consequence of CVE-2022-31096 is that users could bypass email domain restrictions, leading to unauthorized access.
There are no specific workarounds for CVE-2022-31096 other than applying the recommended updates.