Unauthenticated file rename via unvalidated show identifier
Published Dec 1, 2021 · Updated Aug 4, 2024
Path manipulation in LibreTime 3.0.0-alpha.10 allows remote attackers to rename files through a crafted show-image identifier. The REST show-image controller accepts the id parameter without validation, joins it into a storage destination path, and passes that path to rename(). Network access without authentication is sufficient; public evidence does not establish which existing files can be moved or overwritten.
Summary
What happened
Path manipulation in LibreTime 3.0.0-alpha.10 allows remote attackers to rename files through a crafted show-image identifier. The REST show-image controller accepts the id parameter without validation, joins it into a storage destination path, and passes that path to rename(). Network access without authentication is sufficient; public evidence does not establish which existing files can be moved or overwritten.
The record
- CVE
- CVE-2021-43685
- Published
- Dec 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-610, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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