High, CVSS 8.4crates.ioAmendedPublished
Tauri's Updater Private Keys Possibly Leaked via Vite Environment Variables
CVE-2023-46115 · GHSA-2rcp-jvr4-r259
- Affected
- crates.io tauri-cli >= 2.0.0-alpha.0, < 2.0.0-alpha.16; >= 1.0.0, < 1.5.6
- Fixed in
- 2.0.0-alpha.161.5.6· Vendor fix available
- Issue
- Impact 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 possibly leads to bundling the TAURIPRIVATEKEY and TAURIKEYPASSWORD into the Vite frontend code and therefore leaking this value to the debug built of a Tauri application. The value is automatically bundled into debug builds but for production builds it is not embedded, as long as it is not directly referenced in the frontend code. Vite statically replaces these values in production builds. This reduces the amount of affected applications to a very small amount of…
Recommended action: Upgrade to 2.0.0-alpha.16 (pre-release) or 1.5.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.