Update dependency @tauri-apps/cli to v1.5.6 [SECURITY] #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.5.5
->1.5.6
GitHub Vulnerability Alerts
CVE-2023-46115
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 thevite.config.ts
of a Tauri project possibly leads to bundling theTAURI_PRIVATE_KEY
andTAURI_KEY_PASSWORD
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 affected applications.
To verify if you are affected you can search for the private key value or the
TAURI_PRIVATE_KEY
variable inside the release build frontend assets (dist/
).Using only the
envPrefix: ['VITE_'],
or any other framework than Vite means you are not impacted by this advisory.Patches
The documentation has been patched but as the root cause is not in Tauri itself the issue is not fixed by updating Tauri.
The
vite.config.ts
configuration of the project needs to be adapted.We recommend rotating your updater private key if you 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'spubkey
value ontauri.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.Workarounds
The
envPrefix: ['VITE_'],
should be used and the desiredTAURI
variables manually added.Respective these variables could be added
TAURI_PLATFORM
,TAURI_ARCH
,TAURI_FAMILY
,TAURI_PLATFORM_VERSION
,TAURI_PLATFORM_TYPE
andTAURI_DEBUG
without leaking sensitive information.We urge affected users to implement the workaround as the
1.x
branch will not receive a general prevention fix as it would break systems.References
The issue was originally disclosed in our discord here.
The affected guide is https://tauri.app/v1/guides/getting-started/setup/vite/.
Release Notes
tauri-apps/tauri (@tauri-apps/cli)
v1.5.6
: @tauri-apps/api v1.5.6Compare Source
Yarn Audit
[1.5.6]
Bug Fixes
3b69c1384
(#9792) Revert #9706 which broke compatability betweentauri
crate and the JS@tauri-apps/api
npm package in a patch release where it should've been in a minor release.Yarn Publish
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.