How severe is CVE-2002-0687?

No CVSS score has been assigned to CVE-2002-0687 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2002-0687?

CVE-2002-0687 affects the following packages: zope (PyPI), zope (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2002-0687?

Update zope to 2.4.4b2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-0687 is resolved across your whole dependency graph.

How do I detect CVE-2002-0687 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zope, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2002-0687 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2002-0687 actively exploited in the wild?

No public exploit code has been indexed for CVE-2002-0687 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2002-0687?

CVE-2002-0687 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2002-0687 published, and has it been updated?

CVE-2002-0687 was published on April 30, 2022 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2002-0687: zope DoS — Fixed in 2.4.4b2

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍zope🐍zope

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Zope is a Web application server for Linux. Zope versions 2.0 through 2.5.1 b1 are vulnerable to a denial of service attack, caused by a vulnerability that occurs when using the "through the Web code" capability. A remote attacker could inject malicious headers into a response to cause the vulnerable system to crash.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`zope`	≥ 2.0.0&&< 2.4.4b2	2.4.4b2`pip install --upgrade 'zope==2.4.4b2'`
🐍PyPI	`zope`	≥ 2.5.0&&< 2.5.1b2	2.5.1b2`pip install --upgrade 'zope==2.5.1b2'`

Affected Products

1 product · 1 configurations

Application

zopezope

≤ 2.5.1b1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zope, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zope to 2.4.4b2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-0687 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red Hat

RHSA-2002:060Red Hat Powertools 7.0

Frequently Asked Questions

Zope is a Web application server for Linux. Zope versions 2.0 through 2.5.1 b1 are vulnerable to a denial of service attack, caused by a vulnerability that occurs when using the "through the Web code" capability. A remote attacker could inject malicious headers into a response to cause the vulnerable system to crash.

O3 Security · Impact-Aware SCA

Is CVE-2002-0687 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2002-0687 — zope