Loading vulnerability…
CVE-2017-9791 affects the Struts 1 plugin in Apache Struts 2.1.x and 2.3.x. The vulnerability may allow remote code execution when a malicious field value is passed in a raw message to ActionMessage. Based on the available description, the issue is tied to unsafe handling of attacker-controlled input within ActionMessage processing in the Struts 1 compatibility plugin, resulting in execution of unintended code or expressions. Specific vulnerable functions or code paths are not provided in the supplied content.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/http/struts2_code_exec_showcase.rb) that exploits a remote code execution vulnerability (CVE-2017-9791) in Apache Struts 2 (2.3.x series) when the Struts 1 plugin and Showcase application are enabled. The exploit works by sending a specially crafted OGNL expression in an HTTP POST parameter (default: 'name') to a vulnerable endpoint (default: /struts2-showcase/integration/saveGangster.action). The OGNL payload enables arbitrary command execution on the server, with the output returned in the HTTP response. The module is weaponized, supporting customizable payloads and is part of the Metasploit framework. The code is written in Ruby and leverages Metasploit's HttpClient mixin for network communication. The exploit targets Linux, Unix, and Windows platforms.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.