GitHub Advisoryadvisory · crates.io

GHSA-9f3p-wvj7-q82x Cargo prior to Rust 1.26.0 may download the wrong dependency

HIGH Published 2022-05-24 Modified 2024-08-29 Official page ↗
Aliases
CVE-2019-16760
Ecosystem
crates.io
Packages
cargo
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weaknesses
CWE-494
Reviewed
2024-08-29

Affected packages

• crates.io cargo: < 0.27.0 → fixed in 0.27.0

Description

Cargo prior to Rust 1.26.0 may download the wrong dependency if your package.toml file uses the `package` configuration key. Usage of the `package` key to rename dependencies in `Cargo.toml` is ignored in Rust 1.25.0 and prior. When Rust 1.25.0 and prior is used Cargo may download the wrong dependency, which could be squatted on crates.io to be a malicious package. This not only affects manifests that you write locally yourself, but also manifests published to crates.io. Rust 1.0.0 through Rust 1.25.0 is affected by this advisory because Cargo will ignore the `package` key in manifests. Rust 1.26.0 through Rust 1.30.0 are not affected and typically will emit an error because the `package` key is unstable. Rust 1.31.0 and after are not affected because Cargo understands the `package` key. Users of the affected versions are strongly encouraged to update their compiler to the latest available one. Preventing this issue from happening requires updating your compiler to be either Rust 1.26.0 or newer. There will be no point release for Rust versions prior to 1.26.0. Users of Rust 1.19.0 to Rust 1.25.0 can instead apply linked patches to mitigate the issue.

Related

Alias · CVE (1)

  • CVE-2019-16760 Cargo prior to Rust 1.26.0 may download the wrong dependency if your package.toml file uses the `package` configuration key. vulnerability

Weakness · CWE (1)

  • CWE-494 Download of Code Without Integrity Check weakness

References