Headline
GHSA-4wm2-cwcf-wwvp: Tauri Open Redirect Vulnerability Possibly Exposes IPC to External Sites
Impact
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[1].
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.
Patches
This issue has been patched in the latest release and was backported to all previous 1.x releases.
Workarounds
Prevent arbitrary input in redirect features. Only allow trusted websites access to the IPC.
References
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.
Package
cargo tauri (Rust)
Affected versions
>= 1.0.0, < 1.0.9
>= 1.1.0, < 1.1.4
>= 1.2.0, < 1.2.5
Patched versions
1.0.9
1.1.4
1.2.5
Description
Impact
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 redirect1.
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.
Patches
This issue has been patched in the latest release and was backported to all previous 1.x releases.
Workarounds
Prevent arbitrary input in redirect features. Only allow trusted websites access to the IPC.
References
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.
References
- GHSA-4wm2-cwcf-wwvp
- tauri-apps/tauri@9c0593c
- https://en.wikipedia.org/wiki/Open_redirect
- https://github.com/tauri-apps/tauri/releases/tag/tauri-v1.0.9
- https://github.com/tauri-apps/tauri/releases/tag/tauri-v1.1.4
- https://github.com/tauri-apps/tauri/releases/tag/tauri-v1.2.5
- https://tauri.app/v1/api/config/#securityconfig.dangerousremotedomainipcaccess
- https://www.github.com/tauri-apps/tauri/commit/58ea0b45268dbd46cbac0ebb0887353d057ca767
- https://www.github.com/tauri-apps/tauri/commit/fa90214b052b1a5d38d54fbf1ca422b4c37cfd1f
Footnotes
- https://en.wikipedia.org/wiki/Open_redirect ↩
lucasfernog published to tauri-apps/tauri
May 3, 2023
Published to the GitHub Advisory Database
May 3, 2023
Reviewed
May 3, 2023
Last updated
May 3, 2023
Related news
Tauri is software for building applications for multi-platform deployment. The Tauri IPC is usually strictly isolated from external websites, but in versions 1.0.0 until 1.0.9, 1.1.0 until 1.1.4, and 1.2.0 until 1.2.5, 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. 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 versions 1.0.9, 1.1.4, and 1.2.5. As a workaround, prevent arbitrary input in redirect features and/or only allow trusted websites access to the IPC.