Account takeover via undeleted email verification tokens
Published Aug 13, 2021 · Updated Aug 4, 2024
Weak token invalidation in Discourse before 2.7.8 and beta builds before 2.8.0.beta4 allows remote attackers to reset account passwords. EmailChangeRequest lacks dependent destruction for old_email_token and new_email_token, so deleting the request leaves its associated EmailToken valid. An attack requires an unused verification token from an added email address and deletion of that address; reuse grants control of the affected account.
Summary
What happened
Weak token invalidation in Discourse before 2.7.8 and beta builds before 2.8.0.beta4 allows remote attackers to reset account passwords. EmailChangeRequest lacks dependent destruction for old_email_token and new_email_token, so deleting the request leaves its associated EmailToken valid. An attack requires an unused verification token from an added email address and deletion of that address; reuse grants control of the affected account.
The record
- CVE
- CVE-2021-37693
- Published
- Aug 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Discourse
- Product
- Discourse
- Classifications
- CWE-640, CWE-613, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.7.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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