What is CVE-2006-4684?

CVE-2006-4684 is a medium-severity security vulnerability in zope2 (pip), affecting versions >= 2.7.0, <= 2.7.9. It is fixed in 2.8.9.

Which versions of zope2 are affected by CVE-2006-4684?

zope2 (pip) versions >= 2.7.0, <= 2.7.9 is affected.

Is there a fix for CVE-2006-4684?

Yes. CVE-2006-4684 is fixed in 2.8.9. Upgrade to this version or later.

Is CVE-2006-4684 exploitable, and should I be worried?

Whether CVE-2006-4684 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.

What actually determines whether CVE-2006-4684 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.

CVE-2006-4684 in zope2

Q: Which versions of zope2 are affected by CVE-2006-4684?

zope2 (pip) versions >= 2.7.0, <= 2.7.9 is affected.

Q: Is there a fix for CVE-2006-4684?

Yes. CVE-2006-4684 is fixed in 2.8.9. Upgrade to this version or later.

Q: Is CVE-2006-4684 exploitable, and should I be worried?

Whether CVE-2006-4684 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.

Q: What actually determines whether CVE-2006-4684 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.

Q: How do I fix CVE-2006-4684?

Upgrade zope2 to 2.8.9 or later.

Summary

Zope allows remote attackers to read arbitrary files

The docutils module in Zope (Zope2) 2.7.0 through 2.7.9 and 2.8.0 through 2.8.8 does not properly handle web pages with reStructuredText (reST) markup, which allows remote attackers to read arbitrary files via a csv_table directive, a different vulnerability than CVE-2006-3458.

Impact

Affected versions

zope2 (>= 2.7.0, <= 2.7.9) zope2 (>= 2.8.0, < 2.8.9)

Security releases

zope2 → 2.8.9 (pip)

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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade zope2 to 2.8.9 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2006-4684? CVE-2006-4684 is a medium-severity security vulnerability in zope2 (pip), affecting versions >= 2.7.0, <= 2.7.9. It is fixed in 2.8.9.
Which versions of zope2 are affected by CVE-2006-4684? zope2 (pip) versions >= 2.7.0, <= 2.7.9 is affected.
Is there a fix for CVE-2006-4684? Yes. CVE-2006-4684 is fixed in 2.8.9. Upgrade to this version or later.
Is CVE-2006-4684 exploitable, and should I be worried? Whether CVE-2006-4684 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-2006-4684 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-2006-4684? Upgrade zope2 to 2.8.9 or later.

Other vulnerabilities in zope2

CVE-IDSeverityPackage summary

CVE-2011-3587Highzope2: Zope Command Execution Vulnerability CVE-2009-5145MediumZope2: Zope Cross-site scripting (XSS) vulnerability in ZMI pages CVE-2006-3458LowZope2: Zope allows local users to read arbitrary files CVE-2011-4924Mediumzope: Zope XSS Vulnerability CVE-2012-5489HighZope2: Plone and Zope2 vulnerable to unauthorized access to restricted attributes