CVE-2010-3495: Zope Object Database Denial of Service vulnerability

CVE-2010-3495 · Severity: info · Published 2010-10-19

Race condition in ZEO/StorageServer.py in Zope Object Database (ZODB) before 3.10.0 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, a related issue to CVE-2010-3492.

Technologies: zodb3 (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2010-3495 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2010-3495 being exploited in the wild.
How severe is CVE-2010-3495?
Informational severity, published 19 October 2010.
Which products and versions are affected?
zodb3 (PyPI) ECOSYSTEM:introduced=0,fixed=3.10.0a1, ECOSYSTEM:introduced=0,fixed=3.10.0a2.
Is there a fix for CVE-2010-3495?
Yes. zodb3 (PyPI): upgrade to 3.10.0a1, 3.10.0a2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2010-3495?
Check whether you run zodb3 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • zodb3 (PyPI): upgrade to 3.10.0a1, 3.10.0a2 or later
    pip install "zodb3>=3.10.0a2"

Affected products

  • zodb3 (PyPI) ECOSYSTEM:introduced=0,fixed=3.10.0a1, ECOSYSTEM:introduced=0,fixed=3.10.0a2

Identifiers

  • CVE-2010-3495
  • GHSA-j6m4-frxh-p4x8
  • PYSEC-2010-27

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.