LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36447: An issue was discovered in the v9 crate through 2020-12-18 for Rust.

An issue was discovered in the v9 crate through 2020-12-18 for Rust. There is an unconditional implementation of Sync for SyncRef<T>.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-36447 affects the Rust v9 crate. The reported flaw is an unconditional Sync implementation for SyncRef<T>, which can make code appear safe to share across threads when that may not be true. Business urgency depends on whether the crate is in your Rust dependency tree.

Executive priority

Treat this as a targeted Rust dependency hygiene issue. It deserves prompt inventory and remediation if present, but the provided evidence does not support emergency response, active exploitation claims, or broad product exposure.

Technical view

The advisory describes an unconditional implementation of Rust's Sync trait for SyncRef<T> in the v9 crate through 2020-12-18. This is a Rust memory-safety/concurrency concern: incorrect Sync implementations can permit thread-sharing assumptions that violate type safety. The provided sources do not include CVSS, CWE, affected version ranges beyond date wording, exploit details, or a fixed release.

Likely exposure

Exposure is limited to Rust projects that directly or transitively depend on the v9 crate versions described as affected through 2020-12-18. The bundle does not identify broader products, CPEs, cloud services, or internet-facing components.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. No exploit status, proof of concept, or weaponized scenario is provided. Any practical impact likely depends on whether application code uses affected SyncRef<T> behavior in concurrent contexts.

Researcher notes

Evidence is sparse. The key technical fact is an unconditional Sync implementation for SyncRef<T>. No CVSS, CWE, patch version, exploitability analysis, or affected downstream products are present in the supplied bundle. Avoid expanding scope beyond Rust projects using v9.

Mitigation direction

  • Inventory Rust dependencies for the v9 crate.
  • Check RustSec RUSTSEC-2020-0127 and maintainer guidance for fixed or recommended versions.
  • Remove or replace the dependency if no maintained safe version is documented.
  • Prioritize review where v9 is used in multithreaded or shared-state code.
  • Track this as dependency risk rather than an internet-exposed emergency.

Validation and detection

  • Review Cargo.lock and dependency metadata for v9.
  • Confirm whether the version falls under the advisory wording through 2020-12-18.
  • Identify code paths using SyncRef<T> or v9 abstractions across threads.
  • Use Rust dependency audit tooling to detect RUSTSEC-2020-0127.
  • Document whether the dependency is direct, transitive, or absent.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2020-36447 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.