# CVE-2023-31134: Tauri Open Redirect Vulnerability Possibly Exposes IPC to External Sites

> Attackers can bypass IPC isolation via open redirects, exposing internal APIs to external sites in Tauri desktop applications.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 May 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-4wm2-cwcf-wwvp

## What is CVE-2023-31134?

CVE-2023-31134 is a medium-severity vulnerability in tauri-apps tauri, published on 9 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Tauri is software for building applications for multi-platform deployment. The Tauri IPC is usually strictly isolated from external websites, but in versions 1.0.0 until 1.0.9, 1.1.0 until 1.1.4, and 1.2.0 until 1.2.5, 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. 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. This issue has been patched in versions 1.0.9, 1.1.4, and 1.2.5. As a workaround, prevent arbitrary input in redirect features and/or only allow trusted websites access to the IPC.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2023-31134?

6 open source packages ship an affected version, including tauri. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tauri` | crates.io | From 1.0.0 | 1.0.9 |
| `tauri` | crates.io | From 1.0.0 | 1.0.9 |
| `tauri` | crates.io | From 1.1.0 | 1.1.4 |
| `tauri` | crates.io | From 1.1.0 | 1.1.4 |
| `tauri` | crates.io | From 1.2.0 | 1.2.5 |
| `tauri` | crates.io | From 1.2.0 | 1.2.5 |

Products: Tauri Tauri.

## How do I fix CVE-2023-31134?

Upgrade tauri to a fixed version for your release line: 1.0.9, 1.1.4 or 1.2.5.

## Is CVE-2023-31134 being exploited?

There is no known exploitation of CVE-2023-31134 in the wild and no public exploit code.

## Other vulnerabilities in tauri-apps tauri

- [CVE-2023-46115](https://insights.sbomify.com/CVE-2023-46115/): Updater Private Keys Possibly Leaked via Vite Environment Variables in tauri-cli (high 8.4)
- [CVE-2022-39215](https://insights.sbomify.com/CVE-2022-39215/): The readDir Endpoint Scope can be Bypassed With Symbolic Links in Tauri (high 8.3)
- [CVE-2022-46171](https://insights.sbomify.com/CVE-2022-46171/): Tauri vulnerable to path traversal (medium 6.8)
- [CVE-2026-42184](https://insights.sbomify.com/CVE-2026-42184/): Tauri: Origin Confusion Allows Remote Pages to Invoke Local-Only IPC Commands (medium 6.1)
- [CVE-2023-34460](https://insights.sbomify.com/CVE-2023-34460/): Tauri vulnerable to Regression on Filesystem Scope Checks for Dotfiles (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31134 and fix it if it is affected.

What it is: CVE-2023-31134 is a medium-severity vulnerability in tauri-apps tauri, published on 9 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-31134 in the wild and no public exploit code.

Affected packages and fixed versions:
- tauri (crates.io): affected from 1.0.0; fixed in 1.0.9
- tauri (crates.io): affected from 1.0.0; fixed in 1.0.9
- tauri (crates.io): affected from 1.1.0; fixed in 1.1.4
- tauri (crates.io): affected from 1.1.0; fixed in 1.1.4
- tauri (crates.io): affected from 1.2.0; fixed in 1.2.5
- tauri (crates.io): affected from 1.2.0; fixed in 1.2.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31134/ (Markdown: https://insights.sbomify.com/CVE-2023-31134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31134
- OSV: https://osv.dev/vulnerability/CVE-2023-31134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31134/
Summaries are generated and may contain mistakes; the official description above is the record.