Skip to content

← Public intelligence

crates.io package

Tauri

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 2.3crates.ioPublished

    Tauri Filesystem Scope can be Partially Bypassed

    CVE-2022-41874 · GHSA-q9wv-22m9-vhqh

    Affected
    • crates.io Tauri >= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.2
    Fixed in
    1.1.21.0.7· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 1.1.2 or 1.0.7 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →