Summary
Tauri Filesystem Scope can be Partially Bypassed
Workaround
Disable the dialog and fileDropEnabled component inside the tauri.conf.json.
For more information
This issue was initially reported by MessyComposer in #5234.
If you have any questions or comments about this advisory:
Open an issue in tauri
Email us at [email protected]
Impact
Due to incorrect escaping of special characters in paths selected via the file dialog and drag and drop functionality, it was possible to partially bypass the fs scope definition. It was not possible to traverse into arbitrary paths, as the issue was 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.
On Linux or MacOS based systems it was possible to use the *, ** and [a-Z] patterns inside a path, which allowed to read the content of sub directories and single character files in a folder, where only specific files or the directory itself were allowed.
On Windows [a-Z] was the possible bypass pattern, as * is not treated as a valid path component. This implies that only single character files inside an already allowed directory were unintentionally accessible.
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. This means the issue by itself can not be abused and requires further intentional or unintentional privileges.
CVE-2022-41874 has a CVSS score of 2.3 (Low). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.7, 1.1.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue has been resolved in #5237 and the implementation now properly escapes the special characters. The patch has been included in releases: 1.0.7, 1.1.2 and 1.2.0
Frequently Asked Questions
- What is CVE-2022-41874? CVE-2022-41874 is a low-severity security vulnerability in Tauri (rust), affecting versions >= 1.0.0, < 1.0.7. It is fixed in 1.0.7, 1.1.2.
- How severe is CVE-2022-41874? CVE-2022-41874 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of Tauri are affected by CVE-2022-41874? Tauri (rust) versions >= 1.0.0, < 1.0.7 is affected.
- Is there a fix for CVE-2022-41874? Yes. CVE-2022-41874 is fixed in 1.0.7, 1.1.2. Upgrade to this version or later.
- Is CVE-2022-41874 exploitable, and should I be worried? Whether CVE-2022-41874 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-41874 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-41874?
- Upgrade
Taurito 1.0.7 or later - Upgrade
Taurito 1.1.2 or later
- Upgrade