Unauthenticated file read via legacy endpoint path traversal
Published Mar 23, 2021 · Updated Aug 3, 2024
Path traversal in Jellyfin before 10.7.1 allows remote attackers to read arbitrary server files through unauthenticated HTTP requests. Legacy HLS handlers combine attacker-controlled route segments with request-derived extensions and the transcode path without enforcing containment, while image handlers similarly trust theme or name segments. Encoded Windows path separators enable the documented traversal, and disclosure is limited to files readable by the Jellyfin server process.
Summary
What happened
Path traversal in Jellyfin before 10.7.1 allows remote attackers to read arbitrary server files through unauthenticated HTTP requests. Legacy HLS handlers combine attacker-controlled route segments with request-derived extensions and the transcode path without enforcing containment, while image handlers similarly trust theme or name segments. Encoded Windows path separators enable the documented traversal, and disclosure is limited to files readable by the Jellyfin server process.
The record
- CVE
- CVE-2021-21402
- Published
- Mar 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jellyfin
- Product
- Jellyfin
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=< 10.7.1
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
- GitHub Security Lab HTTP request proofs 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