Unexpected session resumption in crypto/tls
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 and 1 more.
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Go standard library | <1.24.13, >=1.25.0-0 <1.25.7, >=1.26.0-rc.1 <1.26.0-rc.3 | 1.24.13, 1.25.7, 1.26.0-rc.3 | |
| go: stdlib | >=1.26.0-rc.1 <1.26.0-rc.3 | 1.26.0-rc.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in stdlib (Go), strongest first
Embed
A live severity badge for an advisory, README or ticket