Loading vulnerability…
CVE-2022-30629 is an insufficient-entropy flaw in Go's crypto/tls implementation before Go 1.17.11 and Go 1.18.3. TLS session tickets use non-random ticket_age_add values, allowing an observer to compare ticket ages during session resumption and correlate a client's successive TLS connections.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
37 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced by the Rocky Linux 9 CIQ crlsa-2022_5799 security update; the supplied content provides no technical details.
A Go vulnerability referenced by the CIQ crlsa-2022_5775 advisory; the provided content does not describe its technical impact.
A low-severity privacy flaw in Go's crypto/tls implementation. Predictable ticket_age_add values in TLS session tickets can enable a network observer to correlate a client's successive resumed TLS connections.
A vulnerability referenced by the AlmaLinux 9.2 local security-check plugin; the content provides no vulnerability-specific technical description.
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.