Tauri vulnerable to path traversal
tauri-apps tauri
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tauri crates.io |
|
|
tauri-apps tauri
| Product | Affected | Fixed in |
|---|---|---|
| tauri crates.io |
|
|
Tauri is a framework for building binaries for all major desktop platforms. The filesystem glob pattern wildcards `*`, `?`, and `[...]` match file path literals and leading dots by default, which unintentionally exposes sub folder content of allowed paths. Scopes without the wildcards are not affected. As `**` allows for sub directories the behavior there is also as expected. The issue has been patched in the latest release and was backported into the currently supported 1.x branches. There are no known workarounds at the time of publication.
From the CVE record · GitHub_M
Tauri filesystem scopes using `*`, `?`, or `[...]` can unintentionally expose content in subfolders of allowed paths because those wildcards match path literals and leading dots by default. An attacker who can use an affected filesystem scope may access that content; the input does not specify whether authentication or user interaction is required. Scopes without those wildcards are unaffected, and `**` behaves as expected.
Check applications using the crates.io `tauri` package in versions >=1.0.0 <1.0.8, >=1.1.0 <1.1.3, >=1.2.0 <1.2.3, or >=2.0.0-alpha.0 <2.0.0-alpha.2.