CVE-2017-7924 is an improper input validation vulnerability in Rockwell Automation MicroLogix 1100 controllers (models 1763-L16BWA, 1763-L16AWA, 1763-L16BBB, and 1763-L16DWD). A remote, unauthenticated attacker can send a specially crafted Programmable Controller Communication Commands (PCCC) packet to the controller, causing it to enter a denial-of-service (DoS) condition. The vulnerability is due to insufficient validation of input data in the PCCC protocol handler.
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 auxiliary DoS module targeting Allen-Bradley MicroLogix 1100 PLCs (models: 1763-L16BWA, 1763-L16AWA, 1763-L16BBB, 1763-L16DWD) running firmware versions 14.00 up to (but not including) 16.00. The exploit leverages CVE-2017-7924, where a specially crafted PCCC packet sent over Ethernet/IP (ENIP) can cause the PLC to enter a Denial of Service state. The module communicates with the PLC over TCP or UDP port 44818, first establishing a session and connection, then sending the malicious packet. The code includes logic to check if the target is vulnerable by querying the device's model and firmware version. The exploit is operational and can be used to disrupt the target PLC's operation, but does not provide a shell or further access. The repository is structured as a single Ruby file compatible with 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.
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.