Tauri is a framework for building binaries for all major desktop platforms. This advisory is not describing a vulnerability in the Tauri code base itself but a commonly used misconfiguration which could lead to leaking of the private key and updater key password into bundled Tauri applications using the Vite frontend in a specific configuration. The Tauri documentation used an insecure example configuration in the Vite guide to showcase how to use Tauri together with Vite. Copying the following snippet envPrefix: [VITE_, TAURI_], from this guide into the vite.config.ts of a Tauri project leads to bundling the TAURI_PRIVATE_KEY and TAURI_KEY_PASSWORD into the Vite frontend code and therefore leaking this value to the released Tauri application. Using the envPrefix: [VITE_], or any other framework than Vite means you are not impacted by this advisory. Users are advised to rotate their updater private key if they are affected by this (requires Tauri CLI >=1.5.5). After updating the envPrefix configuration, generate a new private key with tauri signer generate, saving the new private key and updating the updaters pubkey value on tauri.conf.json with the new public key. To update your existing application, the next application build must be signed with the older private key in order to be accepted by the existing application.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tauri | Tauri | * | 2.0.0 (excluding) |
| Tauri | Tauri | 2.0.0-alpha0 (including) | 2.0.0-alpha0 (including) |
| Tauri | Tauri | 2.0.0-alpha10 (including) | 2.0.0-alpha10 (including) |
| Tauri | Tauri | 2.0.0-alpha11 (including) | 2.0.0-alpha11 (including) |
| Tauri | Tauri | 2.0.0-alpha12 (including) | 2.0.0-alpha12 (including) |
| Tauri | Tauri | 2.0.0-alpha13 (including) | 2.0.0-alpha13 (including) |
| Tauri | Tauri | 2.0.0-alpha14 (including) | 2.0.0-alpha14 (including) |
| Tauri | Tauri | 2.0.0-alpha15 (including) | 2.0.0-alpha15 (including) |
| Tauri | Tauri | 2.0.0-alpha2 (including) | 2.0.0-alpha2 (including) |
| Tauri | Tauri | 2.0.0-alpha3 (including) | 2.0.0-alpha3 (including) |
| Tauri | Tauri | 2.0.0-alpha4 (including) | 2.0.0-alpha4 (including) |
| Tauri | Tauri | 2.0.0-alpha5 (including) | 2.0.0-alpha5 (including) |
| Tauri | Tauri | 2.0.0-alpha6 (including) | 2.0.0-alpha6 (including) |
| Tauri | Tauri | 2.0.0-alpha7 (including) | 2.0.0-alpha7 (including) |
| Tauri | Tauri | 2.0.0-alpha8 (including) | 2.0.0-alpha8 (including) |
| Tauri | Tauri | 2.0.0-alpha9 (including) | 2.0.0-alpha9 (including) |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.