A directory traversal vulnerability in 3S CODESYS Gateway-Server versions before 2.3.9.27 allows remote attackers to execute arbitrary code through vectors involving a crafted pathname.
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 targeting a directory traversal vulnerability (CVE-2012-4705) in the 3S CoDeSys Gateway Server (versions prior to 2.3.9.27) on Windows. The exploit leverages the vulnerability to upload arbitrary files to sensitive locations on the target system. It first uploads a custom EXE payload to the Windows system directory, then uploads a malicious MOF file to the wbem\mof directory, which triggers the execution of the payload via the Windows Management Instrumentation (WMI) service. The exploit is fully integrated into Metasploit, allowing for customizable payloads and automated session handling. The main attack vector is network-based, targeting TCP port 1211. The module is operational and provides remote code execution capabilities on vulnerable SCADA 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.
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.