CVE-2023-31134

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.

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.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2023-31134 has a CVSS score of 4.8 (Medium). The vector is reachable from an adjacent network, low 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.9, 1.1.4, 1.2.5); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been patched in the latest release and was backported to all previous 1.x releases.

1. What is CVE-2023-31134? CVE-2023-31134 is a medium-severity open redirect vulnerability in tauri (rust), affecting versions >= 1.0.0, < 1.0.9. It is fixed in 1.0.9, 1.1.4, 1.2.5. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. How severe is CVE-2023-31134? CVE-2023-31134 has a CVSS score of 4.8 (Medium). 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.
3. Which versions of tauri are affected by CVE-2023-31134? tauri (rust) versions >= 1.0.0, < 1.0.9 is affected.
4. Is there a fix for CVE-2023-31134? Yes. CVE-2023-31134 is fixed in 1.0.9, 1.1.4, 1.2.5. Upgrade to this version or later.
5. Is CVE-2023-31134 exploitable, and should I be worried? Whether CVE-2023-31134 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
6. What actually determines whether CVE-2023-31134 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.
7. How do I fix CVE-2023-31134?
   • Upgrade tauri to 1.0.9 or later
   • Upgrade tauri to 1.1.4 or later
   • Upgrade tauri to 1.2.5 or later