# CVE-2021-20213: Null dereference in privoxy

> A NULL pointer dereference in Privoxy causes a crash when intercepting requests with failed memory allocation, requiring non-default configuration.

- **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:** 25 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2021-20213, DEBIAN-CVE-2021-20213, GHSA-gwg6-gwm3-3g4w, UBUNTU-CVE-2021-20213

## What is CVE-2021-20213?

CVE-2021-20213 is a high-severity vulnerability in privoxy, published on 25 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Privoxy in versions before 3.0.29. Dereference of a NULL-pointer that could result in a crash if accept-intercepted-requests was enabled, Privoxy failed to get the request destination from the Host header and a memory allocation failed.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Privoxy Privoxy.

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

Upgrade to a fixed version.

## Is CVE-2021-20213 being exploited?

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

## Other vulnerabilities in privoxy

- [CVE-2019-3699](https://insights.sbomify.com/CVE-2019-3699/): Local privilege escalation from user privoxy to root (high 7.7)
- [CVE-2021-44540](https://insights.sbomify.com/CVE-2021-44540/): Denial of service in Privoxy (high 7.5)
- [CVE-2021-44541](https://insights.sbomify.com/CVE-2021-44541/): Denial of service in Privoxy (high 7.5)
- [CVE-2021-44542](https://insights.sbomify.com/CVE-2021-44542/): Denial of service in Privoxy (high 7.5)
- [CVE-2021-20209](https://insights.sbomify.com/CVE-2021-20209/): Denial of service in privoxy (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-20213 is a high-severity vulnerability in privoxy, 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-20213 in the wild and no public exploit code.

Affected product: privoxy. 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-20213/ (Markdown: https://insights.sbomify.com/CVE-2021-20213/index.md)
```

## Sources

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

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