Summary
Zope Server vulnerable to DoS via header injection
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.
Impact
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
zope to 2.4.4b2 or later; zope to 2.5.1b2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2002-0687? CVE-2002-0687 is a medium-severity uncontrolled resource consumption vulnerability in zope (pip), affecting versions >= 2.0.0, < 2.4.4b2. It is fixed in 2.4.4b2, 2.5.1b2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- Which versions of zope are affected by CVE-2002-0687? zope (pip) versions >= 2.0.0, < 2.4.4b2 is affected.
- Is there a fix for CVE-2002-0687? Yes. CVE-2002-0687 is fixed in 2.4.4b2, 2.5.1b2. Upgrade to this version or later.
- Is CVE-2002-0687 exploitable, and should I be worried? Whether CVE-2002-0687 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2002-0687 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2002-0687?
- Upgrade
zopeto 2.4.4b2 or later - Upgrade
zopeto 2.5.1b2 or later
- Upgrade