CVE-2022-41921: Discourse chat messages should have a maximum character limit

Published Nov 28, 2022
·
Updated

Discourse is an open-source discussion platform. Prior to version 2.9.0.beta13, users can post chat messages of an unlimited length, which can cause a denial of service for other users when posting huge amounts of text. Users should upgrade to version 2.9.0.beta13, where a limit has been introduced. No known workarounds are available.

Affected Software

13 affected components
Discourse Discourse<2.9.0
Discourse Discourse=2.9.0-beta1
Discourse Discourse=2.9.0-beta10
Discourse Discourse=2.9.0-beta11
Discourse Discourse=2.9.0-beta12
Discourse Discourse=2.9.0-beta2
Discourse Discourse=2.9.0-beta3
Discourse Discourse=2.9.0-beta4
Discourse Discourse=2.9.0-beta5
Discourse Discourse=2.9.0-beta6
Discourse Discourse=2.9.0-beta7
Discourse Discourse=2.9.0-beta8
Discourse Discourse=2.9.0-beta9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2.9.0.beta13

Event History

Nov 28, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2022-41921?

CVE-2022-41921 has a moderate severity rating as it can lead to a denial of service by allowing users to post excessively long messages.

2

How do I fix CVE-2022-41921?

To fix CVE-2022-41921, users should upgrade to Discourse version 2.9.0.beta13 or later, which implements a limit on message length.

3

Which versions of Discourse are affected by CVE-2022-41921?

CVE-2022-41921 affects all versions of Discourse prior to 2.9.0.beta13.

4

What impact does CVE-2022-41921 have on users?

CVE-2022-41921 may cause service disruptions for users when someone posts extremely long messages, potentially overwhelming the platform.

5

Is there a workaround for CVE-2022-41921 before upgrading?

There are no suggested workarounds for CVE-2022-41921 other than upgrading to the patched version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203