CVE-2023-40217
Description
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.)
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
AlmaLinux Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | python3.11-devel-3.11.2-2.el9_2.2.aarch64.rpm |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 7.3.13+dfsg-1 |
| sid | Fixed | 7.3.13+dfsg-1 |
| forky | Fixed | 7.3.13+dfsg-1 |
| bullseye | Fixed | 7.3.5+dfsg-2+deb11u3 |
| bookworm | Fixed | 7.3.11+dfsg-2+deb12u2 |
Red Hat Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | — |
| 8 | Fixed | — |
Rocky Linux Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 8 | Fixed | — |
References
- https://errata.rockylinux.org/RLSA-2023:5994
- https://errata.rockylinux.org/RLSA-2023:5998
- https://access.redhat.com/errata/RHSA-2023:5456
- https://access.redhat.com/errata/RHSA-2023:5462
- https://errata.rockylinux.org/RLSA-2023:5997
- https://errata.rockylinux.org/RLSA-2023:5463
- https://www.suse.com/security/cve/CVE-2023-40217.html
- https://security-tracker.debian.org/tracker/CVE-2023-40217
- https://access.redhat.com/errata/RHSA-2023:5463
- https://bugzilla.redhat.com/2235789
- https://errata.almalinux.org/8/ALSA-2023-5463.html
- https://access.redhat.com/errata/RHSA-2023:5997
- https://errata.almalinux.org/8/ALSA-2023-5997.html
- https://access.redhat.com/errata/RHSA-2023:5994
- https://errata.almalinux.org/8/ALSA-2023-5994.html
- https://access.redhat.com/errata/RHSA-2023:5998
- https://errata.almalinux.org/8/ALSA-2023-5998.html
- https://errata.almalinux.org/9/ALSA-2023-5456.html
- https://errata.almalinux.org/9/ALSA-2023-5462.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.