# CVE-2020-10624: Information disclosure in ControlEdge PLC

> Attackers can intercept session tokens transmitted over the network, potentially leading to unauthorized access to ControlEdge PLC and RTU devices.

- **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:** 26 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xh6g-hp9w-9662

## What is CVE-2020-10624?

CVE-2020-10624 is a high-severity vulnerability in ControlEdge PLC, published on 26 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ControlEdge PLC (R130.2, R140, R150, and R151) and RTU (R101, R110, R140, R150, and R151) exposes a session token on the network.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 2 products.


Products: Honeywell Controledge Plc Firmware, Honeywell Controledge Rtu Firmware.

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

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

## Is CVE-2020-10624 being exploited?

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

## Other vulnerabilities in ControlEdge PLC

- [CVE-2022-30318](https://insights.sbomify.com/CVE-2022-30318/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-10628](https://insights.sbomify.com/CVE-2020-10628/): Information disclosure in ControlEdge PLC (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10624 is a high-severity vulnerability in ControlEdge PLC, published on 26 Jun 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-10624 in the wild and no public exploit code.

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

## Sources

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

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