# CVE-2022-1161: ICSA-22-090-05 Rockwell Automation Logix Controllers

> Attackers can modify user program code in Rockwell Logix controllers by exploiting a separation between readable and executed code locations.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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:** 11 Apr 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-7mvq-cv2x-gv8r

## What is CVE-2022-1161?

CVE-2022-1161 is a critical code injection vulnerability in Rockwell Automation 1768 CompactLogix controllers, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker with the ability to modify a user program may change user program code on some ControlLogix, CompactLogix, and GuardLogix Control systems. Studio 5000 Logix Designer writes user-readable program code to a separate location than the executed compiled code, allowing an attacker to change one and not the other.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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

It affects 24 products.


Products: Rockwellautomation Compact Guardlogix 5370 Firmware, Rockwellautomation Compact Guardlogix 5380 Firmware, Rockwellautomation Compactlogix 1768-L43 Firmware, Rockwellautomation Compactlogix 1768-L45 Firmware, Rockwellautomation Compactlogix 1769-L31 Firmware, Rockwellautomation Compactlogix 1769-L32c Firmware, Rockwellautomation Compactlogix 1769-L32e Firmware, Rockwellautomation Compactlogix 1769-L35cr Firmware, Rockwellautomation Compactlogix 1769-L35e Firmware, Rockwellautomation Compactlogix 5370 L1 Firmware, Rockwellautomation Compactlogix 5370 L2 Firmware, Rockwellautomation Compactlogix 5370 L3 Firmware, Rockwellautomation Compactlogix 5380 Firmware, Rockwellautomation Compactlogix 5480 Firmware, Rockwellautomation Controllogix 5550 Firmware, Rockwellautomation Controllogix 5560 Firmware, Rockwellautomation Controllogix 5570 Firmware, Rockwellautomation Controllogix 5580 Firmware, Rockwellautomation Drivelogix 5730 Firmware, Rockwellautomation Flexlogix 1794-L34 Firmware and 4 more.

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

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

## Is CVE-2022-1161 being exploited?

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

## Other vulnerabilities in Rockwell Automation 1768 CompactLogix controllers

- [CVE-2022-3157](https://insights.sbomify.com/CVE-2022-3157/): Rockwell Automation GuardLogix and ControlLogix controllers Vulnerable to Denial-Of-Service Attack (high 8.6)
- [CVE-2022-1797](https://insights.sbomify.com/CVE-2022-1797/): Rockwell Automation Logix Controllers Uncontrolled Resource Consumption (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1161 is a critical code injection vulnerability in Rockwell Automation 1768 CompactLogix controllers, published on 11 Apr 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-1161 in the wild and no public exploit code.

Affected product: Rockwell Automation 1768 CompactLogix controllers. 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-1161/ (Markdown: https://insights.sbomify.com/CVE-2022-1161/index.md)
```

## Sources

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

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