# CVE-2021-45716: Use after free in n/a

> A use-after-free vulnerability in the rusqlite crate allows attackers to potentially execute arbitrary code or cause a denial of service.

- **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:** 26 Dec 2021
- **Updated:** 4 Aug 2024

## What is CVE-2021-45716?

CVE-2021-45716 is a high-severity use after free vulnerability in n/a, published on 26 Dec 2021. 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 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. create_collation has a use-after-free.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2021-45716?

It affects 1 product.


Products: Rusqlite Project Rusqlite.

## How do I fix CVE-2021-45716?

Upgrade to a fixed version.

## Is CVE-2021-45716 being exploited?

There is no known exploitation of CVE-2021-45716 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-35867](https://insights.sbomify.com/CVE-2020-35867/): 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45716 and fix it if it is affected.

What it is: CVE-2021-45716 is a high-severity use after free vulnerability in n/a, published on 26 Dec 2021. 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-2021-45716 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-2021-45716/ (Markdown: https://insights.sbomify.com/CVE-2021-45716/index.md)
```

## Sources

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

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