We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
| Assigner | mitre |
| Reserved | 2023-08-10 |
| Published | 2023-08-25 |
| Updated | 2024-10-02 |
An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)
https://www.python.org/dev/security/
https://lists.debian.org/debian-lts-announce/2023/09/msg00022.html ([debian-lts-announce] 20230920 [SECURITY] [DLA 3575-1] python2.7 security update)
https://security.netapp.com/advisory/ntap-20231006-0014/
https://lists.debian.org/debian-lts-announce/2023/10/msg00017.html ([debian-lts-announce] 20231011 [SECURITY] [DLA 3614-1] python3.7 security update)
