Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tauri-build-1.2.1.crate: 2 vulnerabilities (highest severity is: 4.8) #3

Open
mend-bolt-for-github bot opened this issue Jan 1, 2024 · 0 comments
Labels
Mend: dependency security vulnerability Security vulnerability detected by Mend

Comments

@mend-bolt-for-github
Copy link
Contributor

mend-bolt-for-github bot commented Jan 1, 2024

Vulnerable Library - tauri-build-1.2.1.crate

build time code to pair with https://crates.io/crates/tauri

Library home page: https://crates.io/api/v1/crates/tauri-build/1.2.1/download

Path to dependency file: /src-tauri/Cargo.toml

Path to vulnerable library: /src-tauri/Cargo.toml

Found in HEAD commit: 953dcf744fda3e978ab5c60652575e62240dc959

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (tauri-build version) Remediation Possible**
CVE-2024-12224 Medium 4.8 idna-0.3.0.crate Transitive N/A*
CVE-2023-31134 Medium 4.8 tauri-build-1.2.1.crate Direct tauri - 1.0.9,1.1.4,1.2.5

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-12224

Vulnerable Library - idna-0.3.0.crate

IDNA (Internationalizing Domain Names in Applications) and Punycode.

Library home page: https://crates.io/api/v1/crates/idna/0.3.0/download

Path to dependency file: /src-tauri/Cargo.toml

Path to vulnerable library: /src-tauri/Cargo.toml

Dependency Hierarchy:

  • tauri-build-1.2.1.crate (Root Library)
    • tauri-utils-1.2.1.crate
      • url-2.3.1.crate
        • idna-0.3.0.crate (Vulnerable Library)

Found in HEAD commit: 953dcf744fda3e978ab5c60652575e62240dc959

Found in base branch: main

Vulnerability Details

"idna" 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with "idna" 0.5.0 or earlier.
Concretely, "example.org" and "xn--example-.org" become equal after processing by "idna" 0.5.0 or earlier. Also, "example.org.xn--" and "example.org." become equal after processing by "idna" 0.5.0 or earlier.
In applications using "idna" (but not in "idna" itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an "xn--"-masked name that turns into the name of the target when processed by "idna" 0.5.0 or earlier.
Remedy
Upgrade to "idna" 1.0.3 or later, if depending on "idna" directly, or to "url" 2.5.4 or later, if depending on "idna" via "url". (This issue was fixed in "idna" 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
When upgrading, please take a moment to read about "alternative Unicode back ends for "idna"" (https://docs.rs/crate/idna_adapter/latest).
If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an "issue" (servo/rust-url#992) about combining them with "url" 2.5.4 and "idna" 1.0.3.
Additional information
This issue resulted from "idna" 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in "revision 33 of UTS 46" (https://www.unicode.org/reports/tr46/tr46-33.html#Modifications).
Acknowledgements
Thanks to kageshiron for recognizing the security implications of this behavior.

Publish Date: 2024-12-09

URL: CVE-2024-12224

CVSS 3 Score Details (4.8)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: High
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: Low
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-h97m-ww89-6jmq

Release Date: 2024-12-09

Fix Resolution: idna - 1.0.0

Step up your Open Source Security Game with Mend here

CVE-2023-31134

Vulnerable Library - tauri-build-1.2.1.crate

build time code to pair with https://crates.io/crates/tauri

Library home page: https://crates.io/api/v1/crates/tauri-build/1.2.1/download

Path to dependency file: /src-tauri/Cargo.toml

Path to vulnerable library: /src-tauri/Cargo.toml

Dependency Hierarchy:

  • tauri-build-1.2.1.crate (Vulnerable Library)

Found in HEAD commit: 953dcf744fda3e978ab5c60652575e62240dc959

Found in base branch: main

Vulnerability Details

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.

Publish Date: 2023-05-09

URL: CVE-2023-31134

CVSS 3 Score Details (4.8)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Adjacent
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: Required
    • Scope: Changed
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: Low
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2023-31134

Release Date: 2023-05-09

Fix Resolution: tauri - 1.0.9,1.1.4,1.2.5

Step up your Open Source Security Game with Mend here

@mend-bolt-for-github mend-bolt-for-github bot added the Mend: dependency security vulnerability Security vulnerability detected by Mend label Jan 1, 2024
@mend-bolt-for-github mend-bolt-for-github bot changed the title tauri-build-1.2.1.crate: 1 vulnerabilities (highest severity is: 5.4) tauri-build-1.2.1.crate: 1 vulnerabilities (highest severity is: 4.8) Sep 8, 2024
@mend-bolt-for-github mend-bolt-for-github bot changed the title tauri-build-1.2.1.crate: 1 vulnerabilities (highest severity is: 4.8) tauri-build-1.2.1.crate: 2 vulnerabilities (highest severity is: 4.8) Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mend: dependency security vulnerability Security vulnerability detected by Mend
Projects
None yet
Development

No branches or pull requests

0 participants