# CVE-2020-27207: Use after free in n/a

> A use-after-free in SQLCipher allows remote attackers to cause denial of service and read unexpected RAM data via crafted SQL commands.

- **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:** No
- **Published:** 26 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x3vj-997j-97hq, UBUNTU-CVE-2020-27207

## What is CVE-2020-27207?

CVE-2020-27207 is a high-severity use after free vulnerability in n/a, published on 26 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zetetic SQLCipher 4.x before 4.4.1 has a use-after-free, related to sqlcipher_codec_pragma and sqlite3Strlen30 in sqlite3.c. A remote denial of service attack can be performed. For example, a SQL injection can be used to execute the crafted SQL command sequence. After that, some unexpected RAM data is read.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Zetetic Sqlcipher.

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

No fix has been published for CVE-2020-27207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-27207 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3119](https://insights.sbomify.com/CVE-2021-3119/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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