CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality Impact
LOW
Integrity Impact
LOW
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
Percentile
29.2%
The Tauri IPC is usually strictly isolated from external websites but 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^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 the latest release and was backported to all previous 1.x
releases.
Prevent arbitrary input in redirect features. Only allow trusted websites access to the IPC.
The feature to enable this behavior in a more constrained way was introduced in the 1.3
release and documentation around this can be found in the documentation.
en.wikipedia.org/wiki/Open_redirect
github.com/advisories/GHSA-4wm2-cwcf-wwvp
github.com/tauri-apps/tauri/commit/9c0593c33af52cd9e00ec784d15f63efebdf039c
github.com/tauri-apps/tauri/releases/tag/tauri-v1.0.9
github.com/tauri-apps/tauri/releases/tag/tauri-v1.1.4
github.com/tauri-apps/tauri/releases/tag/tauri-v1.2.5
github.com/tauri-apps/tauri/security/advisories/GHSA-4wm2-cwcf-wwvp
nvd.nist.gov/vuln/detail/CVE-2023-31134
tauri.app/v1/api/config/#securityconfig.dangerousremotedomainipcaccess
www.github.com/tauri-apps/tauri/commit/58ea0b45268dbd46cbac0ebb0887353d057ca767
www.github.com/tauri-apps/tauri/commit/fa90214b052b1a5d38d54fbf1ca422b4c37cfd1f