Description
The asyncore module in Python before 3.2 does not properly handle unsuccessful calls to the accept function, and does not have accompanying documentation describing how daemon applications should handle unsuccessful calls to the accept function, which makes it easier for remote attackers to conduct denial of service attacks that terminate these applications via network connections.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 11 | python2.7 | 2.7.8-11 | — |
Azure Linux
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Azure Linux 3 | python-py | No fix yet | — |
References
- [oss-security] 20100910 Re: CVE Request -- Python -- accept() implementation in async core is broken => more subcases mailing-list
- http://bugs.python.org/issue6706
- MDVSA-2010:216 vendor-advisory
- oval:org.mitre.oval:def:12111 vdb-entry signature
- [oss-security] 20100924 Re: CVE Request -- Python -- accept() implementation in async core is broken => more subcases mailing-list
- [oss-security] 20100922 Re: CVE Request -- Python -- accept() implementation in async core is broken => more subcases mailing-list
- [oss-security] 20100909 CVE Request -- Python -- accept() implementation in async core is broken => more subcases mailing-list
- MDVSA-2010:215 vendor-advisory