# CVE-2018-17924: Missing authorization in Rockwell Automation

> Unauthenticated attackers can modify IP configurations on Rockwell controllers, causing communication loss and denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2018
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-w6vr-5wrp-c9p7

## What is CVE-2018-17924?

CVE-2018-17924 is a high-severity missing authorization vulnerability in Rockwell Automation, published on 7 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2018-17924?

It affects 16 products.


Products: Rockwellautomation 1756-En2f Series a Firmware, Rockwellautomation 1756-En2f Series B Firmware, Rockwellautomation 1756-En2f Series C Firmware, Rockwellautomation 1756-En2t Series a Firmware, Rockwellautomation 1756-En2t Series B Firmware, Rockwellautomation 1756-En2t Series C Firmware, Rockwellautomation 1756-En2t Series D Firmware, Rockwellautomation 1756-En2tr Series a Firmware, Rockwellautomation 1756-En2tr Series B Firmware, Rockwellautomation 1756-En2tr Series C Firmware, Rockwellautomation 1756-En3tr Series a Firmware, Rockwellautomation 1756-En3tr Series B Firmware, Rockwellautomation 1756-Enbt Firmware, Rockwellautomation 1756-Eweb Series a Firmware, Rockwellautomation 1756-Eweb Series B Firmware, Rockwellautomation Micrologix 1400 Firmware.

## How do I fix CVE-2018-17924?

No fix has been published for CVE-2018-17924 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-17924 being exploited?

There is no known exploitation of CVE-2018-17924 in the wild and no public exploit code.

## Other vulnerabilities in Rockwell Automation

- [CVE-2023-2262](https://insights.sbomify.com/CVE-2023-2262/): Rockwell Automation Select Logix Communication Modules Vulnerable to Email Object Buffer Overflow (critical 9.8)
- [CVE-2023-3595](https://insights.sbomify.com/CVE-2023-3595/): Rockwell Automation ControlLogix Communication Modules Vulnerable to Remote Code Execution (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17924 and fix it if it is affected.

What it is: CVE-2018-17924 is a high-severity missing authorization vulnerability in Rockwell Automation, published on 7 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17924 in the wild and no public exploit code.

Affected product: Rockwell Automation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-17924/ (Markdown: https://insights.sbomify.com/CVE-2018-17924/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-17924
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-17924
- OSV: https://osv.dev/vulnerability/CVE-2018-17924

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-17924/
Summaries are generated and may contain mistakes; the official description above is the record.