What is the CVSS score of CVE-2020-25794?

CVE-2020-25794 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 1.7%.

Is there a public PoC exploit available for CVE-2020-25794?

Yes, a public proof-of-concept exploit is available for CVE-2020-25794. Prioritise patching immediately. EPSS: 1.7%.

Is there a patch available for CVE-2020-25794?

Yes, a patch is available for CVE-2020-25794. Update the affected software to the latest version immediately.

Sized Chunks CVE-2020-25794

HIGH

Memory Leak (CWE-401)

2020-09-19 cve@mitre.org

Information Disclosure Sized Chunks

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Sep 19, 2020 - 21:15 nvd

HIGH 7.5

DescriptionNVD

An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.

AnalysisAI

An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Memory Leak (CWE-401), which allows attackers to exhaust available memory leading to denial of service. An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic. Affected products include: Sized-Chunks Project Sized-Chunks. Version information: through 0.6.2.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Ensure all allocated memory is properly freed. Use RAII patterns or garbage-collected languages.