An integer overflow vulnerability exists in Trihedral Engineering VTScada (formerly VTS) versions 6.5 through 9.x before 9.1.20, 10.x before 10.2.22, and 11.x before 11.1.07. Remote attackers can exploit this flaw by sending a specially crafted request that triggers excessive memory allocation, resulting in a server crash. The vulnerability does not require authentication or user interaction and affects the availability of industrial control systems relying on vulnerable VTScada deployments.
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 auxiliary module (modules/auxiliary/admin/scada/phoenix_command.rb) targeting PhoenixContact PLCs (ILC 15x, 17x, and 39x series) that use a proprietary protocol over TCP. The module allows an attacker to connect to a PLC over the network, read device information (type, firmware, build number), and remotely start or stop the PLC CPU. It uses TCP ports 1962 (for info), 41100 (for ILC 15x/17x CPU control), and 20547 (for ILC 39x CPU control). The exploit is operational, providing real impact (remote start/stop of industrial controllers) but is not weaponized for mass exploitation. The code is written in Ruby and is designed to be run 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.
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.