Skip to content

Open Redirect Possibly Exposes IPC to External Sites

Moderate
lucasfernog published GHSA-4wm2-cwcf-wwvp May 3, 2023

Package

Tauri (Tauri-Apps)

Affected versions

< 1.3
>= 1.0.0, < 1.0.9
>= 1.1.0, < 1.1.4
>= 1.2.0, < 1.2.5

Patched versions

>= 1.3
>= 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.

Footnotes

  1. https://en.wikipedia.org/wiki/Open_redirect ↩

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CVE ID

CVE-2023-31134

Weaknesses

No CWEs