CVE-2023-46115: Tauri's Updater Private Keys Possibly Leaked via Vite Environment Variables
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 updater’s 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.
References
- discord.com/channels/616186924390023171/1164260301655523409
- github.com/advisories/GHSA-2rcp-jvr4-r259
- github.com/tauri-apps/tauri/commit/8b166e9bf82e69ddb3200a3a825614980bd8d433
- github.com/tauri-apps/tauri/security/advisories/GHSA-2rcp-jvr4-r259
- nvd.nist.gov/vuln/detail/CVE-2023-46115
- tauri.app/v1/guides/getting-started/setup/vite/
Detect and mitigate CVE-2023-46115 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →