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.
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.xreleases.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.3releaseand documentation around this can be found in the documentation.
Footnotes
https://en.wikipedia.org/wiki/Open_redirect ↩