Loading vulnerability…
A buffer overflow vulnerability exists in RunTime.exe of Sielco Sistemi Winlog Pro SCADA and Winlog Lite SCADA versions prior to 2.07.18. The flaw can be triggered remotely by sending a specially crafted packet to TCP port 46824, resulting in the possibility of arbitrary code execution. The vulnerability is due to improper bounds checking when processing network packets, allowing attackers to overwrite the EIP and execute arbitrary shellcode. Exploit code is publicly available, and the vulnerability has been confirmed on Windows XP SP2 systems. The issue affects industrial control systems, increasing the risk to critical infrastructure 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 exploit module targeting a buffer overflow vulnerability in Sielco Sistemi Winlog versions 2.07.14 and 2.07.16 (CVE-2012-3815). The exploit targets the Runtime.exe service, which listens on TCP port 46824. By sending a specially crafted packet, the attacker can trigger a buffer overflow and execute arbitrary code on the target system. The module uses an egghunter technique to place and execute the payload, which can be any shellcode supported by Metasploit. The exploit is operational and allows for remote code execution, but the reliability may depend on the specific Winlog project running on the target. The only fingerprintable endpoint is the TCP port 46824, which must be accessible for exploitation. The code is written in Ruby and is structured as a standard Metasploit module.
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.