# CVE-2020-8768: Missing authorization in n/a

> Attackers can read and modify device configuration via an insecure mechanism accessible through the web interface.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 17 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-63gj-7hwv-5q69

## What is CVE-2020-8768?

CVE-2020-8768 is a critical missing authorization vulnerability in n/a, published on 17 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Phoenix Contact Emalytics Controller ILC 2050 BI before 1.2.3 and BI-L before 1.2.3 devices. There is an insecure mechanism for read and write access to the configuration of the device. The mechanism can be discovered by examining a link on the website of the device.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2020-8768?

It affects 2 products.


Products: Phoenixcontact Ilc 2050 Bi-L Firmware, Phoenixcontact Ilc 2050 Bi Firmware.

## How do I fix CVE-2020-8768?

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

## Is CVE-2020-8768 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8768 and fix it if it is affected.

What it is: CVE-2020-8768 is a critical missing authorization vulnerability in n/a, published on 17 Feb 2020. 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-2020-8768 in the wild and no public exploit code.

Affected product: n/a. 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-2020-8768/ (Markdown: https://insights.sbomify.com/CVE-2020-8768/index.md)
```

## Sources

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

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