# CVE-2020-18759: Information disclosure in n/a

> An information disclosure vulnerability in the EPA protocol of the MAC1100 PLC allows attackers to read sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-chm8-x5hx-j7rx

## What is CVE-2020-18759?

CVE-2020-18759 is a high-severity vulnerability in n/a, published on 13 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability exists in the EPA protocol of Dut Computer Control Engineering Co.'s PLC MAC1100.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Dcce Mac1100 Plc Firmware.

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

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

## Is CVE-2020-18759 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18753](https://insights.sbomify.com/CVE-2020-18753/): Privilege escalation in n/a (critical 9.8)
- [CVE-2020-18758](https://insights.sbomify.com/CVE-2020-18758/): Command injection in n/a (critical 9.8)
- [CVE-2020-18754](https://insights.sbomify.com/CVE-2020-18754/): Information disclosure in n/a (high 7.5)
- [CVE-2020-18756](https://insights.sbomify.com/CVE-2020-18756/): Information disclosure in n/a (high 7.5)
- [CVE-2020-18757](https://insights.sbomify.com/CVE-2020-18757/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-18759 is a high-severity vulnerability in n/a, published on 13 Aug 2021. 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-18759 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-18759/ (Markdown: https://insights.sbomify.com/CVE-2020-18759/index.md)
```

## Sources

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

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