Account takeover via uncleared logout token
Published Feb 11, 2025 · Updated Feb 12, 2025
Insufficient session expiration in Misskey before 2025.2.0-alpha.0 allows attackers to reuse a Bull Dashboard login token after logout. The frontend signout function removes local account data without expiring the token cookie; affected releases start at 12.109.0. Access requires the victim to log out and then leave or lend the same browser or device, allowing the next user to access the authenticated Bull Dashboard session.
Summary
What happened
Insufficient session expiration in Misskey before 2025.2.0-alpha.0 allows attackers to reuse a Bull Dashboard login token after logout. The frontend signout function removes local account data without expiring the token cookie; affected releases start at 12.109.0. Access requires the victim to log out and then leave or lend the same browser or device, allowing the next user to access the authenticated Bull Dashboard session.
The record
- CVE
- CVE-2025-24896
- Published
- Feb 11, 2025
- Updated
- Feb 12, 2025
- Vendor
- Misskey Project
- Product
- Misskey
- Classifications
- CWE-613, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 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=>= 12.109.0, < 2025.2.0-alpha.0
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.
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