Skip to content
Fencer Intel
low 2.6

CVE-2022-41874 json

Tauri Filesystem Scope can be Partially Bypassed

published 4y ago modified 4mo ago also GHSA-q9wv-22m9-vhqh , RUSTSEC-2022-0091 , EUVD-2022-7410

cvss
2.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

Tauri is a framework for building binaries for all major desktop platforms. In versions prior to 1.0.7 and 1.1.2, Tauri is vulnerable to an Incorrectly-Resolved Name. Due to incorrect escaping of special characters in paths selected via the file dialog and drag and drop functionality, it is possible to partially bypass the `fs` scope definition. It is not possible to traverse into arbitrary paths, as the issue is limited to neighboring files and sub folders of already allowed paths. The impact differs on Windows, MacOS and Linux due to different specifications of valid path characters. This bypass depends on the file picker dialog or dragged files, as user selected paths are automatically added to the allow list at runtime. A successful bypass requires the user to select a pre-existing malicious file or directory during the file picker dialog and an adversary controlled logic to access these files. The issue has been patched in versions 1.0.7, 1.1.2 and 1.2.0. As a workaround, disable the dialog and fileDropEnabled component inside the tauri.conf.json.

Patch / fix

  • crates.io Tauri 1.0.7, 1.1.2
  • crates.io tauri 1.0.7, 1.1.2
  • tauri tauri 1.0.7, 1.1.2

Is CVE-2022-41874 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 2.6 CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:L/I:N/A:N
NVD 3.1 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
GitHub 3.1 2.3 CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
OSV 3.1 2.3 CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
crates.io Tauri
>=1.0.0, <1.0.7
>=1.1.0, <1.1.2
1.0.7
1.1.2
crates.io tauri
>=1.0.0, <1.0.7
>=1.1.0, <1.1.2
1.0.7
1.1.2

Affected products

  • tauri-apps tauri

Classification

Weakness
  • CWE-668 Exposure of Resource to Wrong Sphere
  • CWE-706 Use of Incorrectly-Resolved Name or Reference
  • CWE-284 Improper Access Control

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.