Memory Leak Vulnerability in Privoxy

privoxy Updated 02 Oct 2025

Summary

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

CVE-2021-20212: A flaw was found in Privoxy in versions before 3.0.29. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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, allowing users to control and modify web page content. However, a vulnerability has been discovered in Privoxy that can lead to a memory leak and system crash.

Vulnerability Detail

The vulnerability (CVE-2021-20212) in Privoxy versions before 3.0.29 arises when multiple filters are executed, and the last one is skipped due to a pcre error. This results in a memory leak, which can exhaust system resources and cause a crash. An attacker could potentially exploit this vulnerability to disrupt the availability of the Privoxy service or execute arbitrary code on the affected system.

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 known workaround for this vulnerability. It is essential to apply the official patch or update to the fixed version to mitigate the risk.

Conclusion

The memory leak vulnerability in Privoxy can have severe consequences, including system crashes and potential code execution. It is crucial to update to the fixed version (3.0.29 or later) or apply the official patch to mitigate the risk. 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 provides advanced filtering capabilities for enhancing privacy, security, and anonymity while browsing the internet.

The vulnerability can lead to a memory leak and system crash, potentially disrupting the availability of the Privoxy service or allowing an attacker to execute arbitrary code on the affected system.

Versions of Privoxy before 3.0.29 are affected by this vulnerability.

No, there is no known workaround. It is crucial to update to the fixed version or apply the official patch.

Users can obtain the fixed version (3.0.29 or later) from the official Privoxy website or through their package manager.

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