# CVE-2021-3119: Null dereference in n/a

> Attackers can cause a remote denial of service via crafted SQL commands triggering a NULL pointer dereference in SQLCipher.

- **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:** 25 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r659-6fh2-v3gv

## What is CVE-2021-3119?

CVE-2021-3119 is a high-severity vulnerability in n/a, published on 25 Mar 2021. 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.3 has a NULL pointer dereferencing issue related to sqlcipher_export in crypto.c and sqlite3StrICmp in sqlite3.c. This may allow an attacker to perform a remote denial of service attack. For example, an SQL injection can be used to execute the crafted SQL command sequence, which causes a segmentation fault.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Zetetic Sqlcipher.

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

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

## Is CVE-2021-3119 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-27207](https://insights.sbomify.com/CVE-2020-27207/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3119 is a high-severity vulnerability in n/a, published on 25 Mar 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-3119 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-3119/ (Markdown: https://insights.sbomify.com/CVE-2021-3119/index.md)
```

## Sources

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

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