Impact
Due to incorrect escaping of special characters in paths selected via the file dialog and drag and drop functionality, it was possible to partially bypass the fs scope definition. It was not possible to traverse into arbitrary paths, as the issue was limited to neighboring files and sub folders of already allowed paths.
The impact differs on Windows, MacOS and Linux due to different specifications of valid path characters.
On Linux or MacOS based systems it was possible to use the *, ** and [a-Z] patterns inside a path, which allowed to read the content of sub directories and single character files in a folder, where only specific files or the directory itself were allowed.
On Windows [a-Z] was the possible bypass pattern, as * is not treated as a valid path component. This implies that only single character files inside an already allowed directory were unintentionally accessible.
This bypass depends on the file picker dialog or dragged files, as user selected paths are automatically added to the allow list at runtime.
A successful bypass requires the user to select a pre-existing malicious file or directory during the file picker dialog and an adversary controlled logic to access these files. This means the issue by itself can not be abused and requires further intentional or unintentional privileges.
Workaround
Disable the dialog and fileDropEnabled component inside the tauri.conf.json.
Patches
The issue has been resolved in #5237 and the implementation now properly escapes the special characters. The patch has been included in releases: 1.0.7, 1.1.2 and 1.2.0
For more information
This issue was initially reported by MessyComposer in #5234.
If you have any questions or comments about this advisory:
Open an issue in tauri
Email us at [email protected]
References
Impact
Due to incorrect escaping of special characters in paths selected via the file dialog and drag and drop functionality, it was possible to partially bypass the
fsscope definition. It was not possible to traverse into arbitrary paths, as the issue was limited to neighboring files and sub folders of already allowed paths.The impact differs on Windows, MacOS and Linux due to different specifications of valid path characters.
On Linux or MacOS based systems it was possible to use the
*,**and[a-Z]patterns inside a path, which allowed to read the content of sub directories and single character files in a folder, where only specific files or the directory itself were allowed.On Windows
[a-Z]was the possible bypass pattern, as*is not treated as a valid path component. This implies that only single character files inside an already allowed directory were unintentionally accessible.This bypass depends on the file picker dialog or dragged files, as user selected paths are automatically added to the allow list at runtime.
A successful bypass requires the user to select a pre-existing malicious file or directory during the file picker dialog and an adversary controlled logic to access these files. This means the issue by itself can not be abused and requires further intentional or unintentional privileges.
Workaround
Disable the
dialogandfileDropEnabledcomponent inside thetauri.conf.json.Patches
The issue has been resolved in #5237 and the implementation now properly escapes the special characters. The patch has been included in releases:
1.0.7,1.1.2and1.2.0For more information
This issue was initially reported by MessyComposer in #5234.
If you have any questions or comments about this advisory:
Open an issue in tauri
Email us at [email protected]
References