CVE-2021-20276Network attack vector

Proxy crash via malformed URL pattern

Published Mar 9, 2021 · Updated Aug 3, 2024

Memory corruption in obsolete PCRE handling in Privoxy before 3.0.32 allows remote attackers to crash the proxy via an invalid URL pattern. The CGI actions editor passes the supplied pattern through get_url_spec_param() and compile_url_pattern() to bundled pcre_compile(), where malformed syntax causes an out-of-bounds write. The editor is disabled by default; when enabled, any user able to reach the proxy can trigger a service interruption.

CVSS severity7.5
High
EPSS probability1.95%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in obsolete PCRE handling in Privoxy before 3.0.32 allows remote attackers to crash the proxy via an invalid URL pattern. The CGI actions editor passes the supplied pattern through get_url_spec_param() and compile_url_pattern() to bundled pcre_compile(), where malformed syntax causes an out-of-bounds write. The editor is disabled by default; when enabled, any user able to reach the proxy can trigger a service interruption.

The record

CVE
CVE-2021-20276
Published
Mar 9, 2021
Updated
Aug 3, 2024
Vendor
Privoxy Developers
Product
Privoxy
Classifications
CWE-119, T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 9, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=privoxy 3.0.32

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Privoxy Developers · Privoxyversion=privoxy 3.0.32

Published CVSS scores

5.0NIST NVDAV:N/AC:L/Au:N/C:N/I:N/A:P
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo