Loading vulnerability…
CVE-2012-0394 is a vulnerability in the DebuggingInterceptor component of Apache Struts versions prior to 2.3.1.1. When developer mode is enabled, remote attackers can execute arbitrary commands via unspecified vectors. The vulnerability arises because developer mode exposes debugging functionality that can be abused to run arbitrary commands on the server. The vendor notes that this is not considered a vulnerability in production deployments, as developer mode should not be enabled outside of development environments.
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/struts_dev_mode.rb) that exploits a remote command execution vulnerability in Apache Struts 2 applications running in developer mode (CVE-2012-0394). The exploit leverages the DebuggingInterceptor, which allows OGNL expression evaluation, to upload and execute a Java JAR payload on the target server. The module is highly weaponized, supporting arbitrary Metasploit Java payloads (such as reverse shells or meterpreter), and is configurable for different target URIs and ports. The main attack vector is network-based, targeting HTTP endpoints exposed by Struts 2 applications. The default vulnerable endpoint is /struts2-blank/example/HelloWorld.action, but this can be changed to match the target application. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.