LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36434: An issue was discovered in the sys-info crate before 0.8.0 for Rust.

An issue was discovered in the sys-info crate before 0.8.0 for Rust. sys_info::disk_info calls can trigger a double free.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-36434 affects the Rust sys-info crate before 0.8.0. Calling disk_info can trigger a double free, a memory-management fault that may crash software or corrupt memory. The public sources do not provide CVSS, affected application contexts, or confirmed exploitation evidence.

Executive priority

Treat this as a dependency hygiene issue with uncertain severity. Upgrade affected software, especially where disk_info is reachable in production services. Escalate priority if internal review finds user-triggered execution or critical service availability impact.

Technical view

The issue is in sys_info::disk_info in sys-info versions before 0.8.0. The documented failure mode is double free. Exposure depends on whether an application depends on sys-info and reaches disk_info during normal or user-influenced execution. No CWE, CVSS vector, exploit details, or exploit-in-the-wild claim is provided.

Likely exposure

Likely exposure is Rust applications or services that include sys-info before 0.8.0 and call sys_info::disk_info. The provided CVE affected-product metadata is not specific, so dependency inventory is required to determine real exposure.

Exploitation context

The source bundle says disk_info calls can trigger the issue. It does not say whether the bug is remotely reachable, reliably exploitable, or only a denial-of-service risk. CISA KEV status is false in the provided bundle.

Researcher notes

Evidence is limited to RustSec and CVE metadata. The key validation question is reachability of sys_info::disk_info. Avoid assuming remote code execution or active exploitation from the available sources.

Mitigation direction

  • Upgrade sys-info to version 0.8.0 or later.
  • Review vendor and RustSec guidance before deployment.
  • Prioritize services where disk_info runs on request paths.
  • Rebuild and redeploy affected Rust applications after dependency updates.

Validation and detection

  • Check Cargo.lock for sys-info versions below 0.8.0.
  • Identify code paths that call sys_info::disk_info.
  • Confirm rebuilt artifacts include sys-info 0.8.0 or later.
  • Run regression tests covering disk information functionality.
Prepared
Confidence
medium
Sources
4

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-36434 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.

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.