Skip to content
Fencer Intel
high 7.5

CVE-2020-35502 json

A flaw was found in Privoxy in versions before 3.0.29.

published 5y ago modified 4mo ago also EUVD-2020-23171

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

A flaw was found in Privoxy in versions before 3.0.29. Memory leaks when a response is buffered and the buffer limit is reached or Privoxy is running out of memory can lead to a system crash.

Patch / fix

  • privoxy privoxy 3.0.29
  • privoxy Debian 14, Debian 13, Debian 12 3.0.29-1

debian advisories DEBIAN-CVE-2020-35502

  • privoxy Ubuntu 16.04 LTS 3.0.24-1ubuntu0.1
  • privoxy Ubuntu 18.04 LTS 3.0.26-5ubuntu0.1
  • privoxy Ubuntu 20.04 LTS 3.0.28-2ubuntu0.1
  • privoxy Ubuntu Pro 14.04 LTS 3.0.21-7+deb8u1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2020-35502

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-35502 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-35502 updated cvss 5.9

privoxy: memory leaks when a response is buffered

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.36% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C

Affected products

  • n/a privoxy

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.