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

> Attackers can violate memory safety in the rusqlite crate via create_module, potentially leading to code execution or crashes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-35867?

CVE-2020-35867 is a critical 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 rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module.

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

It affects 1 product.


Products: Rusqlite Project Rusqlite.

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

Upgrade to a fixed version.

## Is CVE-2020-35867 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35866](https://insights.sbomify.com/CVE-2020-35866/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-35868](https://insights.sbomify.com/CVE-2020-35868/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-35869](https://insights.sbomify.com/CVE-2020-35869/): Other in n/a (critical 9.8)
- [CVE-2020-35870](https://insights.sbomify.com/CVE-2020-35870/): Use after free in n/a (critical 9.8)
- [CVE-2020-35872](https://insights.sbomify.com/CVE-2020-35872/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35867 is a critical 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-35867 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-35867/ (Markdown: https://insights.sbomify.com/CVE-2020-35867/index.md)
```

## Sources

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

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