First published: Thu Sep 09 2010(Updated: )
A race condition was found in the way Python's SMTP proxy module (smtpd.py) processed retrieving of remote IP address the socket was connected to (the other end could close the connection sooner before the requester could get the peername). A remote, unauthenticated user could use this flaw to cause the running python SMTP instance to terminate with uncaught exception by issuing sequence of connection requests within short time interval. References: [1] <a href="http://bugs.python.org/issue9129">http://bugs.python.org/issue9129</a> Upstream patch: [2] <a href="http://svn.python.org/view?view=rev&revision=84289">http://svn.python.org/view?view=rev&revision=84289</a>
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Python Python | =3.1 | |
Python Python | =3.2-alpha | |
debian/python2.5 | ||
debian/python2.6 | ||
debian/python3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3493 is a vulnerability in the smtpd module in Python 2.6, 2.7, 3.1, and 3.2 alpha that 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.
CVE-2010-3493 has a severity rating of medium with a CVSS score of 4.3.
CVE-2010-3493 affects Python 2.6 and 2.7 by allowing remote attackers to cause a denial of service by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None.
CVE-2010-3493 affects Python 3.1 and 3.2 alpha by allowing remote attackers to cause a denial of service by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None.
The solution for CVE-2010-3493 is to update to a patched version of Python or apply the appropriate patch provided by the vendor.