Loading vulnerability…
PortSmash is a microarchitectural timing side-channel vulnerability in processors implementing simultaneous multithreading (SMT), including Hyper-Threading. Shared execution-engine resources permit a malicious process co-located on a sibling logical processor of the victim’s physical core to measure execution-port contention. Applications whose secret-dependent control flow produces distinguishable port use can leak secret-dependent execution behavior. OpenSSL elliptic-curve signing implementations using non-constant-time scalar-multiplication behavior were an affected example; observations can reveal information about nonce processing and may support cryptographic key recovery.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The PortSmash OpenSSL side-channel vulnerability affecting SMT/Hyper-Threading architectures.
An OpenSSL side-channel vulnerability on SMT/Hyper-Threading architectures, also known as PortSmash.
PortSmash is an OpenSSL side-channel vulnerability on SMT/Hyper-Threading architectures.
A side-channel vulnerability in OpenSSL affecting SMT/Hyper-Threading architectures, known as PortSmash.
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.