CVE-2010-3495: Race Condition
Race condition in ZEO/StorageServer.py in Zope Object Database (ZODB) before 3.10.0a2 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.
Other sources
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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3495?
CVE-2010-3495 has been classified as a vulnerability that can lead to a denial of service due to a race condition.
How do I fix CVE-2010-3495?
To fix CVE-2010-3495, upgrade to ZODB version 3.10.0a2 or later.
What systems are affected by CVE-2010-3495?
CVE-2010-3495 affects all versions of Zope Object Database (ZODB) prior to 3.10.0a2.
Can CVE-2010-3495 allow remote attacks?
Yes, CVE-2010-3495 enables remote attackers to cause denial of service by manipulating TCP connections.
What type of issues does CVE-2010-3495 cause?
CVE-2010-3495 can result in daemon outages, impacting service availability.