CVE-2006-3458

CVE-2006-3458 is a low-severity security vulnerability in Zope2 (pip), affecting versions >= 2.7.0, < 2.7.8. It is fixed in 2.7.8, 2.8.7, 2.9.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Zope allows local users to read arbitrary files

Zope 2.7.0 to 2.7.8, 2.8.0 to 2.8.7, and 2.9.0 to 2.9.3 (Zope2) does not disable the "raw" command when providing untrusted users with restructured text (reStructuredText) functionality from docutils, which allows local users to read arbitrary files.

Impact

Affected versions

Zope2 (>= 2.7.0, < 2.7.8) Zope2 (>= 2.8.0, < 2.8.7) Zope2 (>= 2.9.0, < 2.9.3)

Security releases

Zope2 → 2.7.8 (pip) Zope2 → 2.8.7 (pip) Zope2 → 2.9.3 (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 environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Zope2 to 2.7.8 or later; Zope2 to 2.8.7 or later; Zope2 to 2.9.3 or later

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

Frequently Asked Questions

  1. What is CVE-2006-3458? CVE-2006-3458 is a low-severity security vulnerability in Zope2 (pip), affecting versions >= 2.7.0, < 2.7.8. It is fixed in 2.7.8, 2.8.7, 2.9.3.
  2. Which versions of Zope2 are affected by CVE-2006-3458? Zope2 (pip) versions >= 2.7.0, < 2.7.8 is affected.
  3. Is there a fix for CVE-2006-3458? Yes. CVE-2006-3458 is fixed in 2.7.8, 2.8.7, 2.9.3. Upgrade to this version or later.
  4. Is CVE-2006-3458 exploitable, and should I be worried? Whether CVE-2006-3458 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
  5. What actually determines whether CVE-2006-3458 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.
  6. How do I fix CVE-2006-3458?
    • Upgrade Zope2 to 2.7.8 or later
    • Upgrade Zope2 to 2.8.7 or later
    • Upgrade Zope2 to 2.9.3 or later

Other vulnerabilities in Zope2

Stop the waste.
Protect your environment with Kodem.