Loading vulnerability…
A stack-based buffer overflow exists in Sielco Sistemi Winlog Pro version 2.07.00 and earlier. The vulnerability is triggered when the TCP/IP server component, if enabled, receives a specially crafted packet with opcode 0x02 on TCP port 46823. This allows remote attackers to overflow a stack buffer, leading to a crash or potential execution of arbitrary code.
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 Lite (<= 2.07.00), specifically in the Runtime.exe service. The exploit connects to the target on TCP port 46823 and sends a specially crafted packet that overflows a buffer and overwrites the SEH (Structured Exception Handler), allowing arbitrary code execution. The module supports customizable payloads up to 450 bytes, with certain bad characters filtered. The exploit is operational and can be used to gain code execution on vulnerable Windows systems running the affected Winlog version. The repository structure is typical for a Metasploit module, with the main exploit 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.