LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25792: An issue was discovered in the sized-chunks crate through 0.6.2 for Rust.

An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects Rust applications that depend on the sized-chunks crate through 0.6.2. A missing array-size check in Chunk::pair() can cause availability impact. The public sources do not identify active exploitation, exposed services, or affected downstream products.

Executive priority

Prioritize remediation where Rust services are externally reachable or process untrusted input. The issue is high severity for availability, but current evidence does not show active exploitation or broad product impact.

Technical view

CVE-2020-25792 is a CWE-129 issue in sized-chunks where Chunk::pair() does not validate array size during construction. The CVSS 3.1 score is 7.5, driven by network, low-complexity, unauthenticated availability impact. The source bundle identifies an upstream issue and commit but not a specific fixed release.

Likely exposure

Exposure is likely limited to Rust projects that directly or transitively include sized-chunks versions through 0.6.2, especially where untrusted inputs can influence code paths using Chunk construction.

Exploitation context

No source in the bundle states known exploitation, and CISA KEV is false. Treat this as a dependency-risk issue requiring inventory and upgrade review, not as confirmed active compromise.

Researcher notes

Evidence is narrow: the CVE description, RustSec advisory, GitHub issue, and fix commit identify the unchecked array-size condition. The bundle does not provide exploit details, downstream affected products, or a confirmed patched version string.

Mitigation direction

  • Inventory Rust projects for sized-chunks dependency versions through 0.6.2.
  • Review RustSec and upstream repository guidance for the fixed release.
  • Upgrade to a release containing the upstream bounds-check fix.
  • Rebuild and redeploy affected applications after dependency updates.
  • Prioritize internet-facing or untrusted-input services using this dependency.

Validation and detection

  • Check Cargo.lock and SBOMs for sized-chunks through 0.6.2.
  • Identify direct and transitive dependency paths to sized-chunks.
  • Confirm updated builds no longer resolve affected versions.
  • Run existing unit and integration tests after dependency updates.
  • Review application paths that process untrusted data with this crate.
Prepared
Confidence
medium
Sources
5

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.

cwe · low confidence lookup

CWE-129: 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 lookup
cve · low confidence lookup

CVE-2020-25792 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

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

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-25792Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-129

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