Arbitrary file write via unchecked upload path
Published Dec 11, 2024 · Updated Dec 12, 2024
Path traversal in SiYuan before 3.1.16 allows remote attackers to write arbitrary files through the asset upload API. The Upload handler joins the user-controlled assetsDirPath with the data directory, then creates directories and stores uploaded content without verifying that the resolved path remains inside the workspace. Network access to the endpoint is sufficient for file writes; a written web asset can also execute as stored cross-site scripting when viewed.
Summary
What happened
Path traversal in SiYuan before 3.1.16 allows remote attackers to write arbitrary files through the asset upload API. The Upload handler joins the user-controlled assetsDirPath with the data directory, then creates directories and stores uploaded content without verifying that the resolved path remains inside the workspace. Network access to the endpoint is sufficient for file writes; a written web asset can also execute as stored cross-site scripting when viewed.
The record
- CVE
- CVE-2024-55659
- Published
- Dec 11, 2024
- Updated
- Dec 12, 2024
- Vendor
- SiYuan Note
- Product
- SiYuan
- Classifications
- CWE-22, CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- Dec 12, 2024Record 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.16
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