# CVE-2016-8380: Missing authorization in Phoenix Contact ILC PLCs

> Attackers can read and write PLC variables without authentication, potentially compromising industrial control system integrity and availability.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 16 Sep 2024
- **Also known as:** GHSA-23m3-jp2w-3vpp

## What is CVE-2016-8380?

CVE-2016-8380 is a high-severity missing authorization vulnerability in Phoenix Contact ILC PLCs, published on 5 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web server in Phoenix Contact ILC PLCs allows access to read and write PLC variables without authentication.

Weakness: CWE-287 (Improper Authentication), CWE-767 (Access to Critical Private Variable via Public Method)

## Which versions are affected by CVE-2016-8380?

It affects 1 product.


Products: Phoenixcontact Ilc Plcs Firmware.

## How do I fix CVE-2016-8380?

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

## Is CVE-2016-8380 being exploited?

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

Public exploit code:

- Phoenix Contact WebVisit 2985725 - Authentication Bypass (exploitdb)

## Other vulnerabilities in Phoenix Contact ILC PLCs

- [CVE-2016-8366](https://insights.sbomify.com/CVE-2016-8366/): Hardcoded credentials in Phoenix Contact ILC PLCs (high 7.3)
- [CVE-2016-8371](https://insights.sbomify.com/CVE-2016-8371/): Auth bypass in Phoenix Contact ILC PLCs (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8380 and fix it if it is affected.

What it is: CVE-2016-8380 is a high-severity missing authorization vulnerability in Phoenix Contact ILC PLCs, 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-2016-8380 in the wild and no public exploit code.

Affected product: Phoenix Contact ILC PLCs. 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-2016-8380/ (Markdown: https://insights.sbomify.com/CVE-2016-8380/index.md)
```

## Sources

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

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