Account takeover via reusable empty reset code
Published Jan 13, 2025 · Updated Jan 13, 2025
Authentication bypass in NamelessMC Nameless 2.1.2 and earlier allows remote attackers to take over manually validated accounts. The forgot-password route accepts an empty c parameter because manual validation stores reset_code as an empty string rather than NULL. Exploitation requires an account approved through either designated AdminCP permission and grants control of that account.
Summary
What happened
Authentication bypass in NamelessMC Nameless 2.1.2 and earlier allows remote attackers to take over manually validated accounts. The forgot-password route accepts an empty c parameter because manual validation stores reset_code as an empty string rather than NULL. Exploitation requires an account approved through either designated AdminCP permission and grants control of that account.
The record
- CVE
- CVE-2025-22144
- Published
- Jan 13, 2025
- Updated
- Jan 13, 2025
- Vendor
- NamelessMC
- Product
- Nameless
- Classifications
- T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2025CVE publishedPublication date reported by the CVE source.
- Jan 13, 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=<= 2.1.2
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
- NamelessMC empty reset-code proof of conceptproof of concept · 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