Two-factor authentication bypass via unenforced attempt limit
Published Jan 14, 2021 · Updated Aug 3, 2024
Authentication bypass in Discourse 2.6.0 and earlier and 2.7.0 beta1 allows remote attackers to bypass 2FA on certain forms. The 2FA validation path fails to enforce its intended attempt limit for those form submissions, permitting repeated code guesses; public records do not identify the affected controller or limiter defect. Exploitation requires a valid username and password for a 2FA-enabled account, and success exposes only actions available through the affected forms.
Summary
What happened
Authentication bypass in Discourse 2.6.0 and earlier and 2.7.0 beta1 allows remote attackers to bypass 2FA on certain forms. The 2FA validation path fails to enforce its intended attempt limit for those form submissions, permitting repeated code guesses; public records do not identify the affected controller or limiter defect. Exploitation requires a valid username and password for a 2FA-enabled account, and success exposes only actions available through the affected forms.
The record
- CVE
- CVE-2021-3138
- Published
- Jan 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Discourse 2.7.0 rate-limit and 2FA bypass proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo