CVE-2021-3138
First published: Thu Jan 14 2021(Updated: )
In Discourse 2.7.0 through beta1, a rate-limit bypass leads to a bypass of the 2FA requirement for certain forms.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Discourse | <=2.6.0 | |
| Discourse | =2.7.0-beta1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-3138?
CVE-2021-3138 has a medium severity rating as it allows a rate-limit bypass leading to a circumvention of the two-factor authentication requirement.
How do I fix CVE-2021-3138?
To fix CVE-2021-3138, upgrade Discourse to version 2.7.0 or later beyond the beta1 release.
Which versions of Discourse are affected by CVE-2021-3138?
CVE-2021-3138 affects Discourse versions 2.7.0-beta1 and all earlier versions up to 2.6.0.
What impact does CVE-2021-3138 have on user security?
The impact of CVE-2021-3138 allows attackers to bypass two-factor authentication, potentially compromising user accounts.
Is there a workaround for CVE-2021-3138 before upgrading?
There is no official workaround for CVE-2021-3138; upgrading to a patched version is recommended for protection.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/discourse
- canonical/discourse
- version/discourse/2.6.0
- version/discourse/2.7.0-beta1