# CVE-2017-14470: Missing authorization in Allen Bradley

> Unauthenticated attackers can read or modify sensitive PLC data and ladder logic via crafted packets when the keyswitch is in specific states.

- **Severity:** Critical 10.0 (`CVSS:3.0/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:** 5 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w4gc-p2rj-9gx7

## What is CVE-2017-14470?

CVE-2017-14470 is a critical missing authorization vulnerability in Talos Allen Bradley, published on 5 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable access control vulnerability exists in the data, program, and function file permissions functionality of Allen Bradley Micrologix 1400 Series B FRN 21.2 and before. A specially crafted packet can cause a read or write operation resulting in disclosure of sensitive information, modification of settings, or modification of ladder logic. An attacker can send unauthenticated packets to trigger this vulnerability. Required Keyswitch State: REMOTE or PROG or RUN Description: The value 0xffffffff is considered NaN for the Float data type. When a float is set to this value and used in the PLC, a fault is triggered. NOTE: This is not possible through RSLogix.

## Which versions are affected by CVE-2017-14470?

It affects 1 product.


Products: Rockwellautomation Micrologix 1400 B Firmware.

## How do I fix CVE-2017-14470?

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

## Is CVE-2017-14470 being exploited?

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

## Other vulnerabilities in Talos Allen Bradley

- [CVE-2017-14462](https://insights.sbomify.com/CVE-2017-14462/): Missing authorization in Allen Bradley (critical 10.0)
- [CVE-2017-14463](https://insights.sbomify.com/CVE-2017-14463/): Missing authorization in Allen Bradley (critical 10.0)
- [CVE-2017-14464](https://insights.sbomify.com/CVE-2017-14464/): Missing authorization in Allen Bradley (critical 10.0)
- [CVE-2017-14465](https://insights.sbomify.com/CVE-2017-14465/): Missing authorization in Allen Bradley (critical 10.0)
- [CVE-2017-14466](https://insights.sbomify.com/CVE-2017-14466/): Missing authorization in Allen Bradley (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14470 and fix it if it is affected.

What it is: CVE-2017-14470 is a critical missing authorization vulnerability in Talos Allen Bradley, published on 5 Apr 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-2017-14470 in the wild and no public exploit code.

Affected product: Talos Allen Bradley. 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-2017-14470/ (Markdown: https://insights.sbomify.com/CVE-2017-14470/index.md)
```

## Sources

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

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