Loading vulnerability…
Meltdown is a hardware speculative-execution vulnerability in affected microprocessors. During speculative execution of an instruction that performs an access prohibited by instruction or memory permissions, fault delivery can be deferred until retirement. Although the architectural access is ultimately rejected, transient instructions can encode data obtained from privileged memory into microarchitectural cache state. An unprivileged local process can then use a targeted cache side channel to infer contents of privileged kernel-space memory. The issue is also known as speculative execution variant 3.
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 (4 hidden).
This repository is a proof-of-concept (PoC) exploit for the Meltdown vulnerability (CVE-2017-5754) affecting certain CPUs and the Linux kernel. The structure consists of two main directories: 'cache' (demonstrating cache timing) and 'meltdown' (the actual exploit). The 'meltdown' directory contains the main exploit code, which uses speculative execution and cache side-channel techniques to read arbitrary memory from protected kernel space. The exploit is run from the command line, requiring the user to specify a memory address and size. The code is written in C and is intended for research and demonstration purposes, not for weaponization. No network or remote endpoints are involved; the attack vector is purely local, requiring code execution privileges on the target system.
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.
80 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A speculative execution side-channel vulnerability affecting multiple CPU architectures, allowing unauthorized data disclosure across privilege boundaries.
The Meltdown speculative execution vulnerability referenced as one of the CVEs used to detect vulnerable systems.
The Meltdown CPU vulnerability, mentioned in the leaked discussions as an older CVE reference.
A CPU speculative execution vulnerability for which Google references KPTI-based mitigations, including Android and Chrome OS patching.
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.