CVE-2018-17924: Rockwell Automation MicroLogix 1400 Controllers and 1756 ControlLogix Communications Modules An unauthentic...
Rockwell Automation MicroLogix 1400 Controllers and 1756 ControlLogix Communications Modules An unauthenticated, remote threat actor could send a CIP connection request to an affected device, and upon successful connection, send a new IP configuration to the affected device even if the controller in the system is set to Hard RUN mode. When the affected device accepts this new IP configuration, a loss of communication occurs between the device and the rest of the system as the system traffic is still attempting to communicate with the device via the overwritten IP address.
Security readout for executives and security teams
This vulnerability lets an unauthenticated network attacker change the IP configuration of affected Rockwell Automation controllers or communications modules. The likely business impact is loss of communication with industrial equipment, which can disrupt operations. The source bundle does not cite active exploitation or provide remediation details. Exposure is most relevant where affected Rockwell devices are reachable over networks that allow CIP/EtherNet/IP communication. The affected list includes multiple MicroLogix 1400 series and 1756 EtherNet/IP communications modules, with version limits stated in the CVE bundle. Treat as a high-priority OT availability risk if affected devices support production, safety-adjacent, or critical operations. Prioritize asset identification and vendor-guided remediation planning. Urgency is lower where devices are isolated from untrusted networks. Mitigation focus: Inventory Rockwell devices and match model, series, and firmware against the affected list.; Check Rockwell Automation and CISA advisory guidance for vendor-approved fixes or mitigations.; Restrict network access to affected devices to trusted engineering and control-system networks..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
n/aRockwell AutomationMicroLogix 1400 Controllers Series A, all versions, Series B, v21.003 and earlier,Series C, v21.003 and earlier, 1756 ControlLogix EtherNet/IP Communications Modules 1756-ENBT, all versions, 1756-EWEB Series A, all versions Series B, all versions, 1756-EN2F Series A, all versions, Series B, all versions, Series C, v10.10 and earlier, 1756-EN2T, Series A, all versions, Series B, all versions, Series C, all versions, Series D, v10.10 and earlier, 1756-EN2TR, Series A, all versions, Series B, all versions, Series C, v10.10 and earlier, 1756-EN3TR, Series A, all versions, Series B, v10.10 and earlier.Listed
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.