CVE-2011-3923 is a remote command execution vulnerability in Apache Struts 2 before 2.3.1.2. The flaw is in the ParametersInterceptor class, where crafted parameter names containing malicious OGNL expressions can bypass intended security protections. By abusing this weakness, a remote attacker can cause attacker-controlled OGNL to be evaluated and execute arbitrary commands on the underlying server. The issue affects Struts 2 applications using the vulnerable interceptor behavior prior to the fixed release.
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 contains a single Metasploit module (modules/exploits/multi/http/struts_code_exec_parameters.rb) that exploits a remote code execution vulnerability (CVE-2011-3923) in Apache Struts versions prior to 2.3.1.2. The vulnerability arises from the ParametersInterceptor's handling of OGNL expressions, allowing attackers to inject and execute arbitrary Java code via crafted HTTP GET parameters. The module supports exploitation of Windows, Linux, and generic Java targets by uploading and executing a payload (executable or JAR) on the server. The attacker can specify the target URI, parameter name, and other options. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The main attack vector is network-based, targeting HTTP endpoints exposed by vulnerable Struts applications. Notable endpoints include the default action path '/blank-struts2/login.action' and the '/tmp/' directory for payload storage on Linux systems.
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.
1 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.