CVE-2022-41874
2.6 · LOWOverview
CVE-2022-41874 is a low-severity vulnerability affecting tauri tauri. It was published on November 10, 2022 and has a CVSS 3.1 base score of 2.6 (LOW).
This vulnerability has a CVSS 3.1 base score of 2.6, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
Technical Description
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
Remediation
Check the references section for vendor advisories and patches from tauri. Update tauri to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| tauri | tauri | >= 1.0.0, < 1.0.7 | Affected |
Frequently Asked Questions
What is CVE-2022-41874?
CVE-2022-41874 is a low-severity vulnerability affecting tauri tauri. It was published on November 10, 2022 and has a CVSS 3.1 base score of 2.6 (LOW).
How severe is CVE-2022-41874?
This vulnerability has a CVSS 3.1 base score of 2.6, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2022-41874?
Check the references section for vendor advisories and patches from tauri. Update tauri to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2022-41874?
CyberStrike's AI-powered security agents can automatically detect CVE-2022-41874 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2022
View all →Abitrary file access vulnerability in Samsung Email prior to 6.1.60.16 allows attacker to read isola
Vulnerability in the Oracle Solaris product of Oracle Systems (component: Install). The supported ve
PendingIntent hijacking vulnerability in KnoxPrivacyNoticeReceiver prior to SMR Feb-2022 Release 1 a
PendingIntent hijacking vulnerability in CpaReceiver prior to SMR Feb-2022 Release 1 allows local at
PendingIntent hijacking vulnerability in DataUsageReminderReceiver prior to SMR Feb-2022 Release 1 a
An insecure data storage vulnerability allows a physical attacker with root privileges to retrieve T
Redis is an in-memory database that persists on disk. By exploiting weaknesses in the Lua script exe
In JetBrains IntelliJ IDEA before 2022.1 reflected XSS via error messages in internal web server was
In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed
Improper file permissions in the CommandPost, Collector, and Sensor components of Fidelis Network an
In finishDrawingWindow of WindowManagerService.java, there is a possible tapjacking due to improper
In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible