Misskey up to 2024.11.0-alpha.3 Bull Dashboard session expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Misskey. The affected element is an unknown function of the component Bull Dashboard. Performing a manipulation results in session expiration. This vulnerability is reported as CVE-2025-24896. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability, which was classified as critical, was found in Misskey. This affects an unknown code of the component Bull Dashboard. The manipulation with an unknown input leads to a session expiration vulnerability. CWE is classifying the issue as CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Misskey is an open source, federated social media platform. Starting in version 12.109.0 and prior to version 2025.2.0-alpha.0, a login token named `token` is stored in a cookie for authentication purposes in Bull Dashboard, but this remains undeleted even after logout is performed. The primary affected users will be users who have logged into Misskey using a public PC or someone else's device, but it's possible that users who have logged out of Misskey before lending their PC to someone else could also be affected. Version 2025.2.0-alpha.0 contains a fix for this issue.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-24896 since 01/27/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 2025.2.0-alpha.0 eliminates this vulnerability. Applying the patch ba9f295ef2bf31cc90fa587e20b9a7655b7a1824 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 10.102.4
- 12.51.0
- 12.90.0
- 13.3.0
- 13.3.1
- 13.3.2
- 13.3.3
- 13.5.0
- 2023.9.0
- 2023.11.1-beta.1
- 2023.12.1
- 2024.2.0
- 2024.5.0
- 2024.11.0-alpha.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Misskey 2025.2.0-alpha.0
Patch: ba9f295ef2bf31cc90fa587e20b9a7655b7a1824
Timeline
01/27/2025 🔍02/11/2025 🔍
02/11/2025 🔍
02/11/2025 🔍
Sources
Advisory: GHSA-w98m-j6hq-cwjmStatus: Confirmed
CVE: CVE-2025-24896 (🔍)
GCVE (CVE): GCVE-0-2025-24896
GCVE (VulDB): GCVE-100-295257
Entry
Created: 02/11/2025 05:48 PMChanges: 02/11/2025 05:48 PM (66)
Complete: 🔍
Cache ID: 244:FA6:40
No comments yet. Languages: en.
Please log in to comment.