ghsa-9f3p-wvj7-q82x
Vulnerability from github
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.
{ "affected": [ { "package": { "ecosystem": "crates.io", "name": "cargo" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "0.27.0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2019-16760" ], "database_specific": { "cwe_ids": [ "CWE-494" ], "github_reviewed": true, "github_reviewed_at": "2024-08-29T18:03:14Z", "nvd_published_at": "2019-09-30T22:15:00Z", "severity": "HIGH" }, "details": "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.", "id": "GHSA-9f3p-wvj7-q82x", "modified": "2024-08-29T18:03:14Z", "published": "2022-05-24T16:57:30Z", "references": [ { "type": "WEB", "url": "https://github.com/rust-lang/rust/security/advisories/GHSA-phjm-8x66-qw4r" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-16760" }, { "type": "WEB", "url": "https://gist.github.com/pietroalbini/0d293b24a44babbeb6187e06eebd4992" }, { "type": "WEB", "url": "https://groups.google.com/forum/#!topic/rustlang-security-announcements/rVQ5e3TDnpQ" }, { "type": "WEB", "url": "https://groups.google.com/forum/#%21topic/rustlang-security-announcements/rVQ5e3TDnpQ" }, { "type": "WEB", "url": "http://www.openwall.com/lists/oss-security/2019/10/08/3" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ], "summary": "Cargo prior to Rust 1.26.0 may download the wrong dependency" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.