tests-0.0.1.crate: 4 vulnerabilities (highest severity is: 9.3)

[mend-for-github-com]

Vulnerable Library - tests-0.0.1.crate

Path to dependency file: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Path to vulnerable library: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Vulnerabilities

CVE	Severity	CVSS	Exploit Maturity	EPSS	Dependency	Type	Fixed in (tests version)	Remediation Possible**	Reachability
CVE-2020-25575	Critical	9.3	Not Defined	1.2%	failure-0.1.8.crate	Transitive	N/A*	❌
CVE-2019-25010	Critical	9.3	Not Defined	0.2%	failure-0.1.8.crate	Transitive	N/A*	❌
CVE-2021-29932	High	8.2	Not Defined	0.1%	parse_duration-2.1.1.crate	Transitive	N/A*	❌
CVE-2024-12224	Medium	6.3	Not Defined		idna-0.3.0.crate	Transitive	N/A*	❌

*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-2020-25575

Vulnerable Library - failure-0.1.8.crate

Experimental error handling abstraction.

Library home page: https://crates.io/api/v1/crates/failure/0.1.8/download

Path to dependency file: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Path to vulnerable library: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Dependency Hierarchy:

• tests-0.0.1.crate (Root Library)
  • enum-utils-0.1.2.crate
    • ❌ failure-0.1.8.crate (Vulnerable Library)

Found in base branch: master

Vulnerability Details

An issue was discovered in the failure crate through 0.1.5 for Rust. It may introduce "compatibility hazards" in some applications, and has a type confusion flaw when downcasting. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: This may overlap CVE-2019-25010

Publish Date: 2020-09-14

URL: CVE-2020-25575

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 1.2%

CVSS 4 Score Details (9.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: N/A
• Impact Metrics:
  • Confidentiality Impact: N/A
  • Integrity Impact: N/A
  • Availability Impact: N/A

For more information on CVSS4 Scores, click here.

CVE-2019-25010

Vulnerable Library - failure-0.1.8.crate

Experimental error handling abstraction.

Library home page: https://crates.io/api/v1/crates/failure/0.1.8/download

Path to dependency file: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Path to vulnerable library: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Dependency Hierarchy:

• tests-0.0.1.crate (Root Library)
  • enum-utils-0.1.2.crate
    • ❌ failure-0.1.8.crate (Vulnerable Library)

Found in base branch: master

Vulnerability Details

An issue was discovered in the failure crate through 2019-11-13 for Rust. Type confusion can occur when private_get_type_id is overridden.
Mend Note: Converted from WS-2019-0506, on 2021-01-19.

Publish Date: 2020-12-31

URL: CVE-2019-25010

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.2%

CVSS 4 Score Details (9.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: N/A
• Impact Metrics:
  • Confidentiality Impact: N/A
  • Integrity Impact: N/A
  • Availability Impact: N/A

For more information on CVSS4 Scores, click here.

CVE-2021-29932

Vulnerable Library - parse_duration-2.1.1.crate

Parses a duration from a string.

Library home page: https://crates.io/api/v1/crates/parse_duration/2.1.1/download

Path to dependency file: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Path to vulnerable library: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Dependency Hierarchy:

• tests-0.0.1.crate (Root Library)
  • ❌ parse_duration-2.1.1.crate (Vulnerable Library)

Found in base branch: master

Vulnerability Details

An issue was discovered in the parse_duration crate through 2021-03-18 for Rust. It allows attackers to cause a denial of service (CPU and memory consumption) via a duration string with a large exponent.
Mend Note: Converted from WS-2021-0048, on 2021-04-02.

Publish Date: 2021-04-01

URL: CVE-2021-29932

Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.1%

CVSS 4 Score Details (8.2)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: N/A
• Impact Metrics:
  • Confidentiality Impact: N/A
  • Integrity Impact: N/A
  • Availability Impact: N/A

For more information on CVSS4 Scores, click here.

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: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Path to vulnerable library: /spec/fixtures/proxy_wasm_filters/Cargo.toml

Dependency Hierarchy:

• tests-0.0.1.crate (Root Library)
  • url-2.3.1.crate
    • ❌ idna-0.3.0.crate (Vulnerable Library)

Found in base branch: master

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-30

URL: CVE-2024-12224

Threat Assessment

Exploit Maturity: Not Defined

EPSS:

CVSS 4 Score Details (6.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: N/A
• Impact Metrics:
  • Confidentiality Impact: N/A
  • Integrity Impact: N/A
  • Availability Impact: N/A

For more information on CVSS4 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-h97m-ww89-6jmq

Release Date: 2024-12-09

Fix Resolution: idna - 1.0.0