CVE-2010-1870 is a vulnerability in the OGNL expression evaluation mechanism of XWork, as used in Apache Struts 2.0.0 through 2.1.8.1 and products such as Atlassian Fisheye and Crucible. The vulnerability arises from an overly permissive whitelist in OGNL, allowing remote attackers to manipulate server-side context objects by accessing and modifying OGNL context variables such as #context, #_memberAccess, #root, and others. This enables bypassing of the intended protection mechanisms in ParameterInterceptors, specifically the '#' protection, and can lead to unauthorized access or modification of server-side data. This issue is distinct from CVE-2008-6504.
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_code_exec.rb) that exploits a remote code execution vulnerability in Apache Struts versions prior to 2.2.0 (CVE-2010-1870). The exploit leverages improper handling of unicode characters in OGNL expressions to bypass security restrictions and execute arbitrary Java code on the server. The module supports both Linux and Windows targets, automatically staging and executing payloads appropriate for each platform. For Linux, it uploads a base64-encoded ELF binary to /tmp, decodes, and executes it. For Windows, it uses TFTP to stage the payload. The module is highly weaponized, leveraging Metasploit's payload system for customizable post-exploitation. The main attack vector is network-based, targeting HTTP endpoints of Struts applications. The only required input is the URI of a vulnerable Struts action, which is configurable. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file.
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.