641 matches found
CVE-2021-20215
Privoxy (versions before 3.0.29) contains a memory-leak condition in the show-status CGI handler that can lead to a system crash when memory allocations fail. Affected component: Privoxy show-status CGI path. Root cause: memory allocation failure triggers leaks, causing potential denial of servic...
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...
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...
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...
CVE-2021-20214
Privoxy vulnerability CVE-2021-20214 affects Privoxy versions before 3.0.29. The issue is memory leaks in the client-tags CGI handler when client tags are configured and memory allocations fail, which can lead to a system crash. Remediation: upgrade to Privoxy 3.0.29 or later (or apply provided f...
CVE-2021-20214
A flaw was found in Privoxy in versions before 3.0.29. Memory leaks in the client-tags CGI handler when client tags are configured and memory allocations fail can lead to a system crash...
CVE-2021-20214
A flaw was found in Privoxy in versions before 3.0.29. Memory leaks in the client-tags CGI handler when client tags are configured and memory allocations fail can lead to a system crash...
CVE-2021-20214
A flaw was found in Privoxy in versions before 3.0.29. Memory leaks in the client-tags CGI handler when client tags are configured and memory allocations fail can lead to a system crash...
CVE-2021-20213
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...
CVE-2021-20213
CVE-2021-20213 affects Privoxy up to version 3.0.28 (prior to 3.0.29). The flaw is a NULL-pointer dereference that can crash Privoxy and may cause a memory allocation failure when accept-intercepted-requests is enabled and the Host header is not parsed correctly. The vulnerability could manifest ...
CVE-2021-20213
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...
CVE-2021-20213
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...
CVE-2021-20212
CVE-2021-20212 affects Privoxy before version 3.0.29. A memory leak occurs when multiple filters are executed and the last one is skipped due to a PCRE error, potentially leading to a system crash. Remediation: upgrade Privoxy to a newer release (3.0.29+); Gentoo GLSA 202107-16 recommends upgradi...
CVE-2021-20212
A flaw was found in Privoxy in versions before 3.0.29. Memory leak if multiple filters are executed and the last one is skipped due to a pcre error leading to a system crash...
CVE-2021-20212
A flaw was found in Privoxy in versions before 3.0.29. Memory leak if multiple filters are executed and the last one is skipped due to a pcre error leading to a system crash...
CVE-2021-20212
A flaw was found in Privoxy in versions before 3.0.29. Memory leak if multiple filters are executed and the last one is skipped due to a pcre error leading to a system crash...
CVE-2021-20211
A flaw was found in Privoxy in versions before 3.0.29. Memory leak when client tags are active can cause a system crash...
CVE-2021-20211
Privoxy vulnerability CVE-2021-20211 affects Privoxy versions before 3.0.29, where a memory leak when client tags are active can lead to a system crash. This is documented in multiple sources (NVD entry and vendor advisories). The available connected documents specify the affected product and the...