Loading vulnerability…
CVE-2018-3639 is a speculative-execution side-channel vulnerability in modern microprocessors, commonly referred to as Speculative Store Bypass (SSB) or Spectre Variant 4. The issue arises from memory access misprediction: the CPU may speculatively execute a load before an older potentially overlapping store has resolved, effectively bypassing the store buffer dependency check. During this transient window, the load can consume stale data from memory and forward it to dependent speculative operations. Although the CPU later discards the mis-speculated architectural results, the transient execution can leave observable microarchitectural side effects, especially in cache state, which can be measured through side-channel techniques such as FLUSH+RELOAD or PRIME+PROBE. Public reporting indicates affected processors include AMD, ARM, and Intel CPUs to varying degrees, with additional reporting also noting IBM Power8/Power9/System z exposure in some contexts. The vulnerability is particularly relevant where untrusted code can execute in the same privilege domain or process as sensitive data, such as managed runtimes, JIT environments, browser JavaScript engines, sandboxes, and eBPF/JIT-like contexts.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).
This repository is a proof-of-concept (PoC) exploit for CVE-2018-3639, also known as Speculative Store Bypass (Spectre Variant 4). The main code file, 'spectre.c', implements a side-channel attack that leverages speculative execution vulnerabilities in certain x86 CPUs to leak a secret value from memory. The exploit works by manipulating CPU cache behavior and measuring access times to infer the value of a protected string ('PASSWORD_SPECTRE'). The repository includes a Makefile for building the exploit and a README with usage instructions and references. The attack is purely local and requires execution on a vulnerable Linux system. No network or external endpoints are involved; the only fingerprintable endpoint is the local file 'spectre.c'. The exploit demonstrates the vulnerability but does not provide weaponized or operational payloads beyond proof of concept.
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.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CPU speculative execution vulnerability added to Google's mitigation overview in May 2018 and tracked across affected Google products.
A speculative execution vulnerability addressed via SSBD-related mitigations, referenced in Windows mitigation guidance.
One of the Spectre speculative execution techniques that can potentially expose privileged memory to user processes and browser-based JavaScript.
A speculative-execution side-channel vulnerability described as a Spectre technique that can potentially expose sensitive memory.
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.