python accept() implementation in async core is broken
Published Oct 19, 2010
5.0
MEDIUMCVSS 2.0
EPSS 3.21%
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.
Affected products
No data.
No data.
Red Hat Enterprise Linux 4
python
Affected
Red Hat Enterprise Linux 5
python
Affected
Red Hat Enterprise Linux 6
python
Affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 4 | python | Affected | n/a |
| Red Hat Enterprise Linux 5 | python | Affected | n/a |
| Red Hat Enterprise Linux 6 | python | Affected | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
This issue affects the version of the python package as shipped with Red Hat Enterprise Linux 4, 5, and 6. Due to the nature of this flaw, it cannot be fixed in the python language, but must be addressed in each module which calls accept().
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
No CVSS v3.0 score for this CVE.
AV:N/AC:L/Au:N/C:N/I:N/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (11 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 3.21% (0.03206) | 87.72th | v5 (v2026.06.15) |
| Jun 15, 2026 | 3.63% (0.03627) | 88.02th | v5 (v2026.06.15) |
| Mar 30, 2025 | 1.27% (0.01275) | 77.69th | v4 (v2025.03.14) |
| Mar 29, 2025 | 2.55% (0.02552) | 75.76th | v4 (v2025.03.14) |
| Mar 17, 2025 | 1.27% (0.01275) | 78.16th | v4 (v2025.03.14) |
| Dec 12, 2024 | 3.77% (0.03775) | 92.18th | v3 (v2023.03.01) |
| Mar 7, 2023 | 3.77% (0.03775) | 90.42th | v3 (v2023.03.01) |
| Mar 6, 2023 | 1.41% (0.01408) | 72.89th | v2 (v2022.01.01) |
| Mar 2, 2023 | 1.41% (0.01408) | 72.88th | v2 (v2022.01.01) |
| Apr 1, 2022 | 1.41% (0.01408) | 70.87th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.41% (0.01408) | 49.94th | v2 (v2022.01.01) |
No CWE recorded.
References (12)
- http://bugs.python.org/issue6706 x_refsource_CONFIRMPatchVendor Advisory
- http://www.mandriva.com/security/advisories?name=MDVSA-2010:215 vendor-advisoryx_refsource_MANDRIVAThird Party Advisory
- http://www.mandriva.com/security/advisories?name=MDVSA-2010:216 vendor-advisoryx_refsource_MANDRIVAThird Party Advisory
- http://www.openwall.com/lists/oss-security/2010/09/09/6 mailing-listx_refsource_MLISTMailing ListThird Party Advisory
- http://www.openwall.com/lists/oss-security/2010/09/11/2 mailing-listx_refsource_MLISTMailing ListThird Party Advisory
- http://www.openwall.com/lists/oss-security/2010/09/22/3 mailing-listx_refsource_MLISTMailing ListThird Party Advisory
- http://www.openwall.com/lists/oss-security/2010/09/24/3 mailing-listx_refsource_MLISTMailing ListThird Party Advisory
- https://access.redhat.com/security/cve/CVE-2010-3492 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=638330 Issue Tracking
- https://nvd.nist.gov/vuln/detail/CVE-2010-3492
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12111 vdb-entrysignaturex_refsource_OVALThird Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2010-3492
Change history (0)
No recorded changes yet.