Account takeover via predictable password reset token
Published May 17, 2022 · Updated Apr 23, 2025
Weak password recovery in Countly Server before 21.11.4 and 22.0.0 through 22.03.6 allows remote attackers to take over accounts. The forgot handler in frontend/express/libs/members.js derives each reset token by hashing the stored username and full name with a timestamp rather than using random bytes. An attacker must know an account's email address or username and full name; guessing the token permits a password reset and control of that account.
Summary
What happened
Weak password recovery in Countly Server before 21.11.4 and 22.0.0 through 22.03.6 allows remote attackers to take over accounts. The forgot handler in frontend/express/libs/members.js derives each reset token by hashing the stored username and full name with a timestamp rather than using random bytes. An attacker must know an account's email address or username and full name; guessing the token permits a password reset and control of that account.
The record
- CVE
- CVE-2022-29174
- Published
- May 17, 2022
- Updated
- Apr 23, 2025
- Vendor
- Countly
- Product
- Countly Server
- Classifications
- CWE-640, T1098
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 21.11.4
- Affected versionversion=>= 22.0.0, < 22.03.7
What conditions does exploitation require?
What is affected?
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