Loading vulnerability…
IBM Security Guardium 10.0 contains a vulnerability that allows HTTP response splitting. An attacker can craft a malicious URL that, when processed by the server, causes the server to return a split HTTP response. This can be leveraged to manipulate the HTTP headers and body sent to the client.
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.
This repository provides operational exploit code for two critical Apache Solr vulnerabilities: CVE-2017-3164 (SSRF) and CVE-2017-12629 (XXE leading to RCE). The structure includes HTTP request templates (both POST and GET/XXE), a JavaScript-based browser exploit (exploit-javascript.html), and a bash script (installrevshell) that installs and executes a Python reverse shell. The exploits leverage Solr's config API and the RunExecutableListener class to upload and execute arbitrary code on the server. The JavaScript file can be hosted and used for phishing-style attacks, automating the exploitation process when a target visits the page. The endpoints are parameterized for the Solr server's IP, collection name, and attacker's listener details. The payload provides a reverse shell to the attacker, granting remote command execution on the vulnerable Solr server. The repository is well-structured for operational exploitation, with clear separation of payload, exploit templates, and automation scripts.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.