Memory Leak in Privoxy (CVE-2021-20215)

privoxy Updated 02 Oct 2025

Summary

25/03/2021
N/A
Yes i
High
7.5

CVE-2021-20215: A flaw was found in Privoxy in versions before 3.0.29. Memory leaks in the show-status CGI handler when memory allocations fail can lead to a system crash. Affects privoxy versions < 3.0.29-r0. Fixed in 3.0.29-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Privoxy is an open-source web proxy server that provides advanced filtering capabilities for enhancing privacy, security, and anonymity while browsing the internet. It acts as an intermediary between the user's device and the web server, filtering and modifying web page content as per user-defined rules. Privoxy is widely used to block ads, remove tracking cookies, and protect against various web-based threats. However, a vulnerability has been discovered in Privoxy versions before 3.0.29 that can lead to a system crash due to memory leaks in the show-status CGI handler when memory allocations fail.

Vulnerability Detail

The vulnerability (CVE-2021-20215) in Privoxy arises from memory leaks in the show-status CGI handler. When memory allocations fail, the handler does not properly release the allocated memory, leading to a gradual depletion of available memory resources. As a result, the system may eventually crash, causing denial of service. This vulnerability can be exploited by an attacker with network access to the affected Privoxy instance. The impact of this vulnerability can range from service disruption to potential data loss if the system crashes during critical operations.

How To Fix

Minimum fixed version

3.0.29-r0

This is the first release that contains the fix.

sudo apk add --upgrade privoxy

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the fixed version of Privoxy.

Conclusion

In conclusion, the vulnerability (CVE-2021-20215) in Privoxy can lead to system crashes due to memory leaks in the show-status CGI handler. Upgrading to version 3.0.29 or later is crucial to mitigate the risk of service disruption and potential data loss. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for privoxy →

Share this vulnerability

FAQ

Privoxy is an open-source web proxy server that enhances privacy, security, and anonymity while browsing the internet. It filters and modifies web page content based on user-defined rules.

The vulnerability can lead to a system crash due to memory leaks in the show-status CGI handler. This can result in service disruption and potential data loss if the system crashes during critical operations.

An attacker with network access to the affected Privoxy instance can exploit this vulnerability by triggering memory allocations that fail, leading to memory leaks and eventual system crashes.

Yes, upgrading Privoxy to version 3.0.29 or later will fix this vulnerability by addressing the memory leaks in the show-status CGI handler.

No, only versions before 3.0.29 are affected by this vulnerability. It is recommended to upgrade to the fixed version to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for privoxy.

How To Fix

Minimum fixed version

3.0.29-r0

This is the first release that contains the fix.

sudo apk add --upgrade privoxy

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback