Account activation via stale email-domain validation
Published May 24, 2022 · Updated Aug 3, 2024
Email restriction bypass in Mastodon before 3.5.0 allows remote attackers to activate preregistered accounts from newly blocked domains. The User model applied BlacklistedEmailValidator only when an account was created, so an earlier confirmation token remained valid after an administrator blocked its email domain. Exploitation requires a pending account and its previously issued confirmation link, and the consequence is account activation despite the instance's domain restriction.
Summary
What happened
Email restriction bypass in Mastodon before 3.5.0 allows remote attackers to activate preregistered accounts from newly blocked domains. The User model applied BlacklistedEmailValidator only when an account was created, so an earlier confirmation token remained valid after an administrator blocked its email domain. Exploitation requires a pending account and its previously issued confirmation link, and the consequence is account activation despite the instance's domain restriction.
The record
- CVE
- CVE-2022-31263
- Published
- May 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2022CVE 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
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