Skip to content
Fencer Vulns
high 7.5

CVE-2021-20274 json

A flaw was found in privoxy before 3.0.32.

published 2021-03-09 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-7708

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

Summary

A flaw was found in privoxy before 3.0.32. A crash may occur due a NULL-pointer dereference when the socks server misbehaves.

Patch / fix

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

debian advisories DEBIAN-CVE-2021-20274

  • privoxy openSUSE Tumbleweed 3.0.32-2.3
  • privoxy Package Hub 15 SP2 3.0.32-bp152.4.9.1
  • privoxy openSUSE Leap 15.2 3.0.32-lp152.3.9.1

opensuse advisories openSUSE-SU-2024:11193-1openSUSE-SU-2021:0460-1openSUSE-SU-2021:0443-1

  • privoxy Alpine 3.24, Alpine 3.23, Alpine 3.22 +10 more 3.0.32-r0

alpine advisories ALPINE-CVE-2021-20274

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • privoxy Arch Linux 3.0.32-1

arch linux advisories AVG-1656

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-2021-20274 updated cvss 5.9

privoxy: NULL-pointer dereference when the socks server misbehaves

  • 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

1.92% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).

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 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • n/a privoxy

Classification

Weakness

References

Sources

Fencer Vulns 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.