Unexpected session resumption in Go crypto/tls
In Go's crypto/tls, session resumption can incorrectly succeed if the tls.Config trust settings are changed between the original handshake and a resumed handshake. Specifically, if the underlying Config has its ClientCAs or RootCAs fields mutated after the initial handshake, the resumed handshake may be accepted even though a full handshake under the updated configuration should fail. The issue can arise when an application calls Config.Clone() and then mutates the returned configuration, or when it uses Config.GetConfigForClient and returns configurations whose CA pools differ over time. As a result, a client may resume a session with a server it would no longer trust, or a server may resume a session with a client it would no longer accept under mutual TLS policy.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
56 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Go crypto/tls session management flaw where Config.Clone incorrectly copies auto-generated session ticket keys, potentially enabling unintended/unauthorized TLS session resumption due to key reuse/sharing behavior.
A crypto/tls vulnerability in Go where Config.Clone can leak auto-generated session ticket keys (enabling unauthorized session resumption across configs) and certificate validation logic fails to consider full certificate chain expiration.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.