What is CVE-2009-2701?

CVE-2009-2701 is a critical-severity security vulnerability in zodb3 (pip), affecting versions >= 3.8, < 3.8.3. It is fixed in 3.8.3, 3.9.0c2.

How severe is CVE-2009-2701?

CVE-2009-2701 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of zodb3 are affected by CVE-2009-2701?

zodb3 (pip) versions >= 3.8, < 3.8.3 is affected.

Is there a fix for CVE-2009-2701?

Yes. CVE-2009-2701 is fixed in 3.8.3, 3.9.0c2. Upgrade to this version or later.

Is CVE-2009-2701 exploitable, and should I be worried?

Whether CVE-2009-2701 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-2009-2701 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-2009-2701?

Upgrade: zodb3 to 3.8.3 or later, zodb3 to 3.9.0c2 or later.

CVE-2009-2701 in zodb3

Q: How severe is CVE-2009-2701?

CVE-2009-2701 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of zodb3 are affected by CVE-2009-2701?

zodb3 (pip) versions >= 3.8, < 3.8.3 is affected.

Q: Is there a fix for CVE-2009-2701?

Yes. CVE-2009-2701 is fixed in 3.8.3, 3.9.0c2. Upgrade to this version or later.

Q: Is CVE-2009-2701 exploitable, and should I be worried?

Whether CVE-2009-2701 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-2009-2701 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-2009-2701?

Upgrade: zodb3 to 3.8.3 or later, zodb3 to 3.9.0c2 or later.

Summary

Zope Object Database (ZODB) Arbitrary files reading and deletion

Unspecified vulnerability in the Zope Enterprise Objects (ZEO) storage-server functionality in Zope Object Database (ZODB) 3.8 before 3.8.3 and 3.9.x before 3.9.0c2, when certain ZEO database sharing and blob support are enabled, allows remote authenticated users to read or delete arbitrary files via unknown vectors.

Impact

CVE-2009-2701 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.8.3, 3.9.0c2); upgrading removes the vulnerable code path.

Affected versions

zodb3 (>= 3.8, < 3.8.3) zodb3 (>= 3.9a0, < 3.9.0c2)

Security releases

zodb3 → 3.8.3 (pip) zodb3 → 3.9.0c2 (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 the following packages to resolve this vulnerability:

zodb3 to 3.8.3 or later; zodb3 to 3.9.0c2 or later

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

Frequently Asked Questions

What is CVE-2009-2701? CVE-2009-2701 is a critical-severity security vulnerability in zodb3 (pip), affecting versions >= 3.8, < 3.8.3. It is fixed in 3.8.3, 3.9.0c2.
How severe is CVE-2009-2701? CVE-2009-2701 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of zodb3 are affected by CVE-2009-2701? zodb3 (pip) versions >= 3.8, < 3.8.3 is affected.
Is there a fix for CVE-2009-2701? Yes. CVE-2009-2701 is fixed in 3.8.3, 3.9.0c2. Upgrade to this version or later.
Is CVE-2009-2701 exploitable, and should I be worried? Whether CVE-2009-2701 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-2009-2701 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-2009-2701?
- Upgrade zodb3 to 3.8.3 or later
- Upgrade zodb3 to 3.9.0c2 or later

Other vulnerabilities in zodb3

CVE-IDSeverityPackage summary

CVE-2010-3495Mediumzodb3: Zope Object Database Denial of Service vulnerability CVE-2009-0668CriticalZODB3: Zope Object Database (ZODB) vulnerable to arbitrary Python code execution in ZEO storage servers CVE-2009-0669HighZODB3: Zope Object Database (ZODB) Authentication bypass in ZEO storage servers