# CVE-2020-25792: Integer overflow in n/a

> An unchecked array size in the Rust sized-chunks crate can lead to memory corruption, potentially causing crashes or arbitrary code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Sep 2020
- **Updated:** 5 May 2025
- **Also known as:** DEBIAN-CVE-2020-25792, UBUNTU-CVE-2020-25792

## What is CVE-2020-25792?

CVE-2020-25792 is a high-severity vulnerability in n/a, published on 19 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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().

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2020-25792?

It affects 1 product.


Products: Sized-Chunks Project Sized-Chunks.

## How do I fix CVE-2020-25792?

Upgrade to a fixed version.

## Is CVE-2020-25792 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25792 exists.

## Other vulnerabilities in n/a

- [CVE-2020-25791](https://insights.sbomify.com/CVE-2020-25791/): Integer overflow in n/a (high 7.5)
- [CVE-2020-25793](https://insights.sbomify.com/CVE-2020-25793/): Integer overflow in n/a (high 7.5)
- [CVE-2020-25794](https://insights.sbomify.com/CVE-2020-25794/): Memory corruption in n/a (high 7.5)
- [CVE-2020-25795](https://insights.sbomify.com/CVE-2020-25795/): Memory corruption in n/a (high 7.5)
- [CVE-2020-25796](https://insights.sbomify.com/CVE-2020-25796/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25792 and fix it if it is affected.

What it is: CVE-2020-25792 is a high-severity vulnerability in n/a, published on 19 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25792 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25792/ (Markdown: https://insights.sbomify.com/CVE-2020-25792/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25792
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25792
- OSV: https://osv.dev/vulnerability/CVE-2020-25792

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25792/
Summaries are generated and may contain mistakes; the official description above is the record.