diff options
| author | Łukasz Langa <lukasz@langa.pl> | 2023-08-22 17:53:15 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-08-22 17:53:15 (GMT) |
| commit | 0cb0c238d520a8718e313b52cffc356a5a7561bf (patch) | |
| tree | 4f250f175ccf9ee94b9c39fb4df67dc72feeef60 /Objects/structseq.c | |
| parent | d2879f2095abd5c8186c7f69c964a341c2053572 (diff) | |
| download | cpython-0cb0c238d520a8718e313b52cffc356a5a7561bf.zip cpython-0cb0c238d520a8718e313b52cffc356a5a7561bf.tar.gz cpython-0cb0c238d520a8718e313b52cffc356a5a7561bf.tar.bz2 | |
gh-108310: Fix CVE-2023-40217: Check for & avoid the ssl pre-close flaw (#108315)
Instances of `ssl.SSLSocket` were vulnerable to a bypass of the TLS handshake
and included protections (like certificate verification) and treating sent
unencrypted data as if it were post-handshake TLS encrypted data.
The vulnerability is caused when a socket is connected, data is sent by the
malicious peer and stored in a buffer, and then the malicious peer closes the
socket within a small timing window before the other peers’ TLS handshake can
begin. After this sequence of events the closed socket will not immediately
attempt a TLS handshake due to not being connected but will also allow the
buffered data to be read as if a successful TLS handshake had occurred.
Co-authored-by: Gregory P. Smith [Google LLC] <greg@krypto.org>
Diffstat (limited to 'Objects/structseq.c')
0 files changed, 0 insertions, 0 deletions
