Rockwell Automation MicroLogix 1400 Controllers and 1756 ControlLogix Communications Modules An unauthenticated, remote threat actor could s
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.3% (FIRST EPSS); higher than 91% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 7, 2018
- Updated
- Jun 16, 2026
- EPSS
- 4.3% · 91th percentile
- CWE
- CWE-306
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rockwellautomation | micrologix 1400 firmware | cpe:2.3:o:rockwellautomation:micrologix_1400_firmware |
| rockwellautomation | micrologix 1400 | cpe:2.3:h:rockwellautomation:micrologix_1400 |
| rockwellautomation | 1756-enbt firmware | cpe:2.3:o:rockwellautomation:1756-enbt_firmware |
| rockwellautomation | 1756-enbt | cpe:2.3:h:rockwellautomation:1756-enbt |
| rockwellautomation | 1756-eweb series a firmware | cpe:2.3:o:rockwellautomation:1756-eweb_series_a_firmware |
| rockwellautomation | 1756-eweb series a | cpe:2.3:h:rockwellautomation:1756-eweb_series_a |
| rockwellautomation | 1756-eweb series b firmware | cpe:2.3:o:rockwellautomation:1756-eweb_series_b_firmware |
| rockwellautomation | 1756-eweb series b | cpe:2.3:h:rockwellautomation:1756-eweb_series_b |
| rockwellautomation | 1756-en2f series a firmware | cpe:2.3:o:rockwellautomation:1756-en2f_series_a_firmware |
| rockwellautomation | 1756-en2f series a | cpe:2.3:h:rockwellautomation:1756-en2f_series_a |
| rockwellautomation | 1756-en2f series b firmware | cpe:2.3:o:rockwellautomation:1756-en2f_series_b_firmware |
| rockwellautomation | 1756-en2f series b | cpe:2.3:h:rockwellautomation:1756-en2f_series_b |
and 20 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rockwellautomation 1756-en2f series a firmwareall versions
- rockwellautomation 1756-en2f series b firmwareall versions
- rockwellautomation 1756-en2f series c firmwareup to 10.10 inclusive
- rockwellautomation 1756-en2t series a firmwareall versions
- rockwellautomation 1756-en2t series b firmwareall versions
- rockwellautomation 1756-en2t series c firmwareall versions
- rockwellautomation 1756-en2t series d firmwareup to 10.10 inclusive
- rockwellautomation 1756-en2tr series a firmwareall versions
- rockwellautomation 1756-en2tr series b firmwareall versions
- rockwellautomation 1756-en2tr series c firmwareup to 10.10 inclusive
- rockwellautomation 1756-en3tr series a firmwareall versions
- rockwellautomation 1756-en3tr series b firmwareup to 10.10 inclusive
- rockwellautomation 1756-enbt firmwareall versions
- rockwellautomation 1756-eweb series a firmwareall versions
- rockwellautomation 1756-eweb series b firmwareall versions
- rockwellautomation micrologix 1400 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
n/a Rockwell Automation
- MicroLogix 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-EWEBaffected
Same product
rockwellautomation: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-22659Rockwell Automation MicroLogix 1400 Version 21.6 and below may allow a remote unauthenticated attacker to send a specially crafted Modbus pa35Monitor
- CVE-2022-46670Rockwell Automation MicroLogix 1100 & 1400 Vulnerable to Cross-Site Scripting Attack24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
nvd-primary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support teamapp.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) { app.post( "/maintenance/reset", requireSession, requireRole("admin"), resetDevice );}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.