# CVE-2020-35893: Memory corruption in n/a

> An off-by-one error in the simple-slab crate allows attackers to leak memory or drop uninitialized data, potentially causing crashes or information disclosure.

- **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:** 31 Dec 2020
- **Updated:** 4 Aug 2024

## What is CVE-2020-35893?

CVE-2020-35893 is a high-severity memory corruption vulnerability in n/a, published on 31 Dec 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 simple-slab crate before 0.3.3 for Rust. remove() has an off-by-one error, causing memory leakage and a drop of uninitialized memory.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Simple-Slab Project Simple-Slab.

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

Upgrade to a fixed version.

## Is CVE-2020-35893 being exploited?

There is no known exploitation of CVE-2020-35893 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-35892](https://insights.sbomify.com/CVE-2020-35892/): Other in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35893 is a high-severity memory corruption vulnerability in n/a, published on 31 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-35893 in the wild and no public exploit code.

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-35893/ (Markdown: https://insights.sbomify.com/CVE-2020-35893/index.md)
```

## Sources

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

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