Use-after-free of a server-side SSLContext when sni_callback switches contexts
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.10.22, 3.11.17, 3.12.15 and 3 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Python Software Foundation | <3.10.22, >=3.11.0 <3.11.17, >=3.12.0 <3.12.15, >=3.13.0 <3.13.16, >=3.14.0 <3.14.8, >=3.15.0a1 <3.15.0rc3 | 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, 3.15.0rc3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket