Spectre Variant 2 is a speculative-execution side-channel vulnerability in modern microprocessors that use indirect branch prediction. By poisoning branch prediction structures such as the branch target buffer, an attacker able to run code on a vulnerable system can influence the speculative target of indirect branches executed by a victim context, including across privilege and isolation boundaries such as process-to-process, user-to-kernel, guest-to-host, or guest-to-guest in some environments. Although mis-speculated instructions are eventually rolled back architecturally, transient execution can leave observable cache and microarchitectural side effects that disclose sensitive data through side-channel analysis. The issue affects multiple processor families, including Intel, AMD, and Arm implementations, and is commonly tracked as Spectre Variant 2 or Branch Target Injection.
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.
4 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (7 hidden).
This repository is a proof-of-concept (PoC) exploit chain targeting Cisco routers vulnerable to CVE-2017-6736 (SNMP RCE) and chaining it with a Spectre (CVE-2017-5753, CVE-2017-5715) browser attack. The structure includes a batch script (readyGo.bat) that automates the exploitation process: it runs a Python-based SNMP RCE exploit (from a submodule), then uses Plink to send configuration commands (from ciscoCommands.txt) to the router, setting a new default route to 195.20.52.49 (an attacker-controlled host). The attacker then serves a fake login page (index.html) that loads JavaScript from the spectre-chrome submodule, attempting a Spectre attack in the browser context. The repository is organized with submodules for the main exploit components, a batch script for automation, and HTML/JS files for the phishing/Spectre phase. The exploit requires access to a vulnerable Cisco router and aims to redirect user traffic through a malicious gateway, where further browser-based exploitation can occur.
This repository is a proof-of-concept (PoC) implementation of the Spectre speculative execution attack (CVE-2017-5753, CVE-2017-5715). The main code is in 'src/main.cpp', which demonstrates how an attacker can use branch prediction and cache timing side-channels to read memory contents that should be inaccessible, specifically leaking a hardcoded secret string. The exploit is local and requires the attacker to run code on the target machine. The repository includes build scripts for various platforms (macOS, Linux, Solaris, Windows), but the exploit is only tested on macOS, Linux, and Solaris. The attack does not target a network service or remote endpoint, but rather exploits CPU hardware vulnerabilities. The structure is typical for a C++ project, with CMake build files, shell scripts for building and running, and a single main source file containing the exploit logic. The exploit is not weaponized and serves as a demonstration of the vulnerability.
This repository contains a proof-of-concept (POC) exploit for the Spectre vulnerability (CVE-2017-5753 and CVE-2017-5715), affecting many Intel CPUs. The repository consists of a README.md (with background and references) and a single C source file (source.c) implementing the attack. The exploit demonstrates how speculative execution and cache timing can be abused to leak memory contents from the same process. The code places a secret string in memory and uses a combination of branch misprediction and cache probing to read the secret, printing the results to standard output. There are no network or remote attack vectors; the exploit is purely local and requires the attacker to execute code on the target system. The code is a classic educational POC and does not weaponize the attack for real-world exploitation, but it clearly demonstrates the underlying vulnerability.
This repository is a proof-of-concept implementation of the Spectre attack (CVE-2017-5753 and CVE-2017-5715) in C. The main code is in 'Source.c', which demonstrates how speculative execution and cache timing side-channels can be exploited to leak memory contents from protected areas. The exploit works by training the branch predictor to mispredict, then performing an out-of-bounds read in speculative execution, and finally using cache timing to infer the value of the secret data. The README provides detailed background, build instructions, and usage examples. The exploit is run locally and does not target network endpoints; it is designed to demonstrate the vulnerability on affected CPUs. The repository contains standard build files (.gitignore, Makefile), documentation (README.md), and the exploit code (Source.c).
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.
48 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Spectre-class speculative execution vulnerability referenced as one of the CVEs used to detect vulnerable systems.
The Spectre Variant 2 CPU vulnerability, mentioned in the discussions as an older CVE of interest.
A CPU speculative execution vulnerability tracked by Google as one of the core flaws covered by product mitigations across Google products and services.
A Spectre speculative execution vulnerability referenced in mitigation guidance.
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.