CVE-2019-16760
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Exploit Intelligence
Moderate risk: more likely to be exploited than 67% of all known CVEs.
References
Related Vulnerabilities
Other CWE-16 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2004-2687 | High | 9.3 | 88% | - | Fix |
| CVE-2009-2335 | Medium | 5.0 | 85% | - | Fix |
| CVE-2006-3677 | High | 7.5 | 78% | - | Fix |
| CVE-2011-4404 | Medium | 5.0 | 60% | - | - |
| CVE-2006-0848 | Medium | 5.1 | 58% | - | - |
| CVE-2007-3898 | Medium | 6.4 | 52% | - | - |
Common questions
How do I fix CVE-2019-16760?
Published advisories record a fix for 3 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2019-16760 being actively exploited?
Not that we know of. CVE-2019-16760 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.3% is the estimated probability that it will be exploited in the next 30 days. That is higher than 67% of all scored CVEs.
How severe is CVE-2019-16760?
CVE-2019-16760 has a CVSS v3 base score of 4.6, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2019-16760 affect?
Published advisories record a fix for cargo (Debian), Rust (GNU) (Windows application), Rust (MSVC) (Windows application). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2019-16760
Markdown
[](https://tridentstack.com/cve/CVE-2019-16760)HTML
<a href="https://tridentstack.com/cve/CVE-2019-16760"><img src="https://tridentstack.com/cve/badge/CVE-2019-16760.svg" alt="CVE-2019-16760"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.