Security readout for executives and security teams
Plain-English summary
This CVE affects the Rust model crate. Its Shared structure can be marked safe to send or share between threads even when the contained value is not thread-safe. In affected code paths, that can undermine Rust's normal safety guarantees and create unpredictable application behavior.
Executive priority
Treat this as a targeted dependency risk, not an internet-wide emergency. Prioritize review if production Rust services use the model crate in concurrent paths or if the dependency is unmaintained.
Technical view
The issue is an unsound Send and Sync implementation for Shared that ignores the inner type's thread-safety requirements. If Shared wraps a non-Send or non-Sync type and is used across threads, Rust's compile-time guarantees can be bypassed, creating possible data races or undefined behavior.
Likely exposure
Exposure is likely limited to Rust projects that depend on the model crate through 2020-11-10 and use Shared, especially in concurrent or multi-threaded contexts. The source bundle does not identify downstream products or package versions beyond the crate/date scope.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Practical impact depends on whether an application uses Shared around non-thread-safe inner types and exposes reachable concurrent behavior.
Researcher notes
Evidence is sparse: no CVSS, CWE, affected version range, exploit report, or vendor patch is included in the source bundle. The core issue is Rust soundness: unsafe trait implementations can invalidate compiler-enforced thread-safety assumptions.
Mitigation direction
- Inventory Rust dependencies for the model crate.
- Check RustSec and crate maintainer guidance for fixed or replacement versions.
- Avoid Shared around non-thread-safe inner types in concurrent code.
- Replace or remove the dependency if no maintained fix is available.
Validation and detection
- Review Cargo.lock and dependency manifests for model crate usage.
- Search code for Shared usages from the model crate.
- Assess whether Shared crosses thread boundaries or async worker boundaries.
- Confirm wrapped inner types satisfy Send and Sync expectations.
Public sources used
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.
CVE-2020-36460 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://rustsec.org/advisories/RUSTSEC-2020-0140.htmlCVE reference · x_refsource_MISC
- https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/model/RUSTSEC-2020-0140.mdCVE 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.