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.
| Vendor | Product | Versions |
|---|---|---|
| golang | go | < 1.24.13, < 1.25.7 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| amazon | amazon linux | cert_advisory | 90% |
| golang | go | cert_advisory | 90% |
| ibm | ibm app connect enterprise | cert_advisory | 90% |
| oracle | oracle linux | cert_advisory | 90% |
| red hat | red hat enterprise linux | cert_advisory | 90% |
