# CVE-2022-3166: MicroLogix 1100 & 1400 Product Web Server Application Vulnerable to Denial-Of-Service Condition Attack

> An attacker can cause a denial-of-service condition on MicroLogix controllers by sending abrupt TCP packets to the web server.

- **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:** 16 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-c9wc-p58w-qcgf

## What is CVE-2022-3166?

CVE-2022-3166 is a high-severity denial of service vulnerability in Rockwell Automation MicroLogix 1100, published on 16 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rockwell Automation was made aware that the webservers of the Micrologix 1100 and 1400 controllers contain a vulnerability that may lead to a denial-of-service condition. The security vulnerability could be exploited by an attacker with network access to the affected systems by sending TCP packets to webserver and closing it abruptly which would cause a denial-of-service condition for the web server application on the device

Weakness: CWE-924 (Improper Enforcement of Message Integrity During Transmission in a Communication Channel)

## Which versions are affected by CVE-2022-3166?

It affects 2 products.


Products: Rockwellautomation Micrologix 1100 Firmware, Rockwellautomation Micrologix 1400 Firmware.

## How do I fix CVE-2022-3166?

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

## Is CVE-2022-3166 being exploited?

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

## Other vulnerabilities in Rockwell Automation MicroLogix 1100

- [CVE-2020-6984](https://insights.sbomify.com/CVE-2020-6984/): Weak cryptography in Rockwell Automation MicroLogix 1400 Controllers Series B v21.001 and prior, Series A, all versions, MicroLogix 1100 Controller, all versions, RSLogix 500 Software v12.001 and prior (critical 9.8)
- [CVE-2020-6990](https://insights.sbomify.com/CVE-2020-6990/): Hardcoded credentials in Rockwell Automation MicroLogix 1400 Controllers Series B v21.001 and prior, Series A, all versions, MicroLogix 1100 Controller, all versions, RSLogix 500 Software v12.001 and prior (critical 9.8)
- [CVE-2015-6490](https://insights.sbomify.com/CVE-2015-6490/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-33012](https://insights.sbomify.com/CVE-2021-33012/): Denial of service in Rockwell Automation MicroLogix 1100 (high 7.5)
- [CVE-2020-6988](https://insights.sbomify.com/CVE-2020-6988/): Information disclosure in Rockwell Automation MicroLogix 1400 Controllers Series B v21.001 and prior, Series A, all versions, MicroLogix 1100 Controller, all versions, RSLogix 500 Software v12.001 and prior (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3166 and fix it if it is affected.

What it is: CVE-2022-3166 is a high-severity denial of service vulnerability in Rockwell Automation MicroLogix 1100, published on 16 Dec 2022. 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-2022-3166 in the wild and no public exploit code.

Affected product: Rockwell Automation MicroLogix 1100. 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-2022-3166/ (Markdown: https://insights.sbomify.com/CVE-2022-3166/index.md)
```

## Sources

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

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