Duplicate account creation via registration race
Published Feb 22, 2024 · Updated Mar 20, 2025
Race condition in Apache Answer 1.2.1 and earlier allows remote attackers to create duplicate accounts through concurrent registrations. The registration flow checks and writes a username without synchronizing concurrent requests, allowing simultaneous submissions to persist the same name. No authentication or user interaction is required, but exploitation depends on winning the timing race and affects account-record integrity.
Summary
What happened
Race condition in Apache Answer 1.2.1 and earlier allows remote attackers to create duplicate accounts through concurrent registrations. The registration flow checks and writes a username without synchronizing concurrent requests, allowing simultaneous submissions to persist the same name. No authentication or user interaction is required, but exploitation depends on winning the timing race and affects account-record integrity.
The record
- CVE
- CVE-2024-26578
- Published
- Feb 22, 2024
- Updated
- Mar 20, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Answer
- Classifications
- CWE-362
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2024CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=0 <=1.2.1
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