Security readout for executives and security teams
Older Rust/Cargo toolchains could fetch a different dependency than the one intended when a manifest uses dependency renaming. In a realistic attack, a malicious lookalike package on crates.io could be pulled during builds. This is mainly a legacy build-chain exposure, not a typical internet-facing server flaw. Exposure is most likely in old CI images, developer workstations, reproducible-build containers, or pinned legacy toolchains using Rust/Cargo 1.25.0 or earlier. Risk requires manifests that use dependency renaming through the package key, including manifests published to crates.io. Treat this as a moderate-priority supply-chain hygiene issue. It is important for organizations with old Rust build infrastructure, but urgency is lower if all builds already use modern Rust toolchains and dependency sources are controlled. Mitigation focus: Upgrade Rust/Cargo build environments to Rust 1.26.0 or newer.; Prefer current supported Rust toolchains where operationally possible.; For Rust 1.19.0 through 1.25.0, review the linked mitigation patches..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-16: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-16760 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L1.23.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.6MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/rust-lang/rust/security/advisories/GHSA-phjm-8x66-qw4rCVE reference · x_refsource_CONFIRM
- https://groups.google.com/forum/#%21topic/rustlang-security-announcements/rVQ5e3TDnpQCVE reference · x_refsource_MISC
- https://gist.github.com/pietroalbini/0d293b24a44babbeb6187e06eebd4992CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Configuration
Configuration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.