GHSA-4wm2-cwcf-wwvp CVE-2023-31134
Tauri Open Redirect Vulnerability Possibly Exposes IPC to External Sites
- Severity
- 4.8 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.52%
- Chance of exploitation in the next 30 days. Higher than 44.49% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-601 URL Redirection to Untrusted Site ('Open Redirect')
- Fix
1.0.9- Upgrade tauri to this version or later
Description
Impact
The Tauri IPC is usually strictly isolated from external websites but the isolation can be bypassed by redirecting an existing Tauri window to an external website. This is either possible by an application implementing a feature for users to visit arbitrary websites or due to a bug allowing the open redirect^open-redirect.
This allows the external website access to the IPC layer and therefore to all configured and exposed Tauri API endpoints and application specific implemented Tauri commands.
Patches
This issue has been patched in the latest release and was backported to all previous 1.x releases.
Workarounds
Prevent arbitrary input in redirect features. Only allow trusted websites access to the IPC.
References
The feature to enable this behavior in a more constrained way was introduced in the 1.3 release and documentation around this can be found in the documentation.
Affected versions
crates.io
| Package | Vulnerable | Fixed in |
|---|---|---|
| tauri | >= 1.0.0, < 1.0.9 |
1.0.9 |
| tauri | >= 1.1.0, < 1.1.4 |
1.1.4 |
| tauri | >= 1.2.0, < 1.2.5 |
1.2.5 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
tauri crates.io → 1.0.9
- cargo
cargo update -p tauri --precise 1.0.9
Severity breakdown
CVSS 3.1 4.8
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
How to prevent it
- Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. Use a list of approved URLs or domains to be used for redirection.
- Architecture and Design: Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
- Architecture and Design: When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs. For example, ID 1 could map to "/login.asp" and ID 2 could map to "http://www.example.com/". Features such as the ESAPI AccessReferenceMap [REF-45] provide this capability.
- Architecture and Design: Ensure that no externally-supplied requests are honored by requiring that all redirect requests include a unique nonce generated by the application [REF-483]. Be sure that the nonce is not predictable (CWE-330).
- Architecture and Design, Implementation: Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls. Many open redirect problems occur because the programmer assumed that certain inputs could not be modified, such as cookies and hidden form fields.
- Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
References
Advisories
Packages
Other links
- github.com/tauri-apps/tauri/security/advisories/GHSA-4wm2-cwcf-wwvp
- github.com/tauri-apps/tauri/commit/9c0593c33af52cd9e00ec784d15f63efebdf039c
- en.wikipedia.org/wiki/Open_redirect
- github.com/tauri-apps/tauri/releases/tag/tauri-v1.0.9
- github.com/tauri-apps/tauri/releases/tag/tauri-v1.1.4
- github.com/tauri-apps/tauri/releases/tag/tauri-v1.2.5
- tauri.app/v1/api/config
- github.com/tauri-apps/tauri/commit/58ea0b45268dbd46cbac0ebb0887353d057ca767
- github.com/tauri-apps/tauri/commit/fa90214b052b1a5d38d54fbf1ca422b4c37cfd1f
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-7gmj-67g7-phm9 Tauri has an Origin Confusion Issue that Allows Remote Pages to Invoke Local-Only IPC Commands | High | Also affects tauri |
| GHSA-57fm-592m-34r7 iFrames Bypass Origin Checks for Tauri API Access Control | Medium | Also affects tauri |
| GHSA-wmff-grcw-jcfm Tauri vulnerable to Regression on Filesystem Scope Checks for Dotfiles | Critical | Also affects tauri |
| GHSA-6mv3-wm7j-h4w5 Tauri Filesystem Scope Glob Pattern is too Permissive | High | Also affects tauri |
| GHSA-q9wv-22m9-vhqh Tauri Filesystem Scope can be Partially Bypassed | Medium | Also affects tauri |
| GHSA-28m8-9j7v-x499 Tauri's readDir Endpoint Scope can be Bypassed With Symbolic Links | Medium | Also affects tauri |
| GHSA-pfhg-q3qv-9q6r SvelteKit: URL redirection to untrusted site via enhanced form submission | Medium | Same weakness, CWE-601 |
| GHSA-w84c-53h3-mc2g Payload: Untrusted redirect URL parameter exploit | Medium | Same weakness, CWE-601 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor