Описание
A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected. Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected.
Пакеты
| Пакет | Статус | Версия исправления | Релиз | Тип |
|---|---|---|---|---|
| python3.15 | fixed | 3.15.0~rc3-1 | package | |
| python3.14 | fixed | 3.14.8-1 | package | |
| python3.13 | fixed | 3.13.18-1 | package | |
| python3.13 | no-dsa | trixie | package | |
| python3.11 | removed | package | ||
| pypy3 | fixed | 8.0.1+dfsg-1 | package | |
| pypy3 | no-dsa | trixie | package | |
| pypy3 | postponed | bookworm | package |
Примечания
https://github.com/python/cpython/issues/156293
https://github.com/python/cpython/pull/158504
https://github.com/python/cpython/commit/63fab143d94cafae71850831acfb52041ba44af7 (v3.15.0rc3)
https://github.com/python/cpython/commit/cd7e51e7d4563866fbaa1e2521ae69b45daf3698 (v3.14.8)
https://github.com/python/cpython/commit/d8717ed01717a9641686e6e6f83f0ab8af235e2c (v3.13.16)
https://github.com/python/cpython/pull/158523 (3.11)
EPSS
Связанные уязвимости
A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected. Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected.
A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected. Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected.
A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected. Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected.
Use-after-free of a server-side SSLContext when sni_callback switches contexts
EPSS