Arbitrary file deletion via unchecked history path
Published Jan 3, 2025 · Updated Jan 3, 2025
Arbitrary file deletion in SiYuan Note 3.1.18 allows remote attackers to delete server files through a crafted history request. The getDocHistoryContent flow accepts an absolute historyPath outside the workspace and calls os.RemoveAll when that file fails JSON parsing. No authentication or user interaction is required, and deletion is limited to files the SiYuan process can access.
Summary
What happened
Arbitrary file deletion in SiYuan Note 3.1.18 allows remote attackers to delete server files through a crafted history request. The getDocHistoryContent flow accepts an absolute historyPath outside the workspace and calls os.RemoveAll when that file fails JSON parsing. No authentication or user interaction is required, and deletion is limited to files the SiYuan process can access.
The record
- CVE
- CVE-2025-21609
- Published
- Jan 3, 2025
- Updated
- Jan 3, 2025
- Vendor
- SiYuan Note
- Product
- SiYuan
- Classifications
- CWE-552, CWE-459, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2025CVE publishedPublication date reported by the CVE source.
- Jan 3, 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== 3.1.18
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
- GHSA getDocHistoryContent curl 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