Directory listing disclosure via recursive symlink traversal
Published Sep 15, 2022 · Updated Apr 22, 2025
Path traversal in Tauri before 1.0.6 allows remote attackers to expose directory listings outside the configured filesystem scope. The readDir endpoint recursively follows a symbolic link or Windows junction under an allowed path without rechecking the resolved child path against the filesystem scope. The endpoint must be enabled and an attacker-controlled link must exist within scope; only names and metadata are exposed, not arbitrary file contents.
Summary
What happened
Path traversal in Tauri before 1.0.6 allows remote attackers to expose directory listings outside the configured filesystem scope. The readDir endpoint recursively follows a symbolic link or Windows junction under an allowed path without rechecking the resolved child path against the filesystem scope. The endpoint must be enabled and an attacker-controlled link must exist within scope; only names and metadata are exposed, not arbitrary file contents.
The record
- CVE
- CVE-2022-39215
- Published
- Sep 15, 2022
- Updated
- Apr 22, 2025
- Vendor
- Tauri Apps
- Product
- Tauri
- Classifications
- CWE-22, CWE-548, CWE-59, T1083
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=< 1.0.6
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
- Windows junction readDir scope-bypass reproductionproof 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