# CVE-2021-32982: Automation Direct CLICK PLC CPU Modules Cleartext Transmission of Sensitive Information

> Attackers with network visibility can observe plaintext passwords during unlocking and project transfers on Automation Direct CLICK PLC CPU Modules.

- **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:** 4 Apr 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-qf82-v8c9-p3px

## What is CVE-2021-32982?

CVE-2021-32982 is a high-severity vulnerability in Automation Direct CLICK PLC CPU Modules: C0-1x CPUs, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Automation Direct CLICK PLC CPU Modules: C0-1x CPUs with firmware prior to v3.00 passwords are sent as plaintext during unlocking and project transfers. An attacker who has network visibility can observe the password exchange.

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

## Which versions are affected by CVE-2021-32982?

It affects 20 products.


Products: Automationdirect C0-10are-D Firmware, Automationdirect C0-10dd1e-D Firmware, Automationdirect C0-10dd2e-D Firmware, Automationdirect C0-10dre-D Firmware, Automationdirect C0-11are-D Firmware, Automationdirect C0-11dd1e-D Firmware, Automationdirect C0-11dd2e-D Firmware, Automationdirect C0-11dre-D Firmware, Automationdirect C0-12are-1-D Firmware, Automationdirect C0-12are-2-D Firmware, Automationdirect C0-12are-D Firmware, Automationdirect C0-12dd1e-1-D Firmware, Automationdirect C0-12dd1e-2-D Firmware, Automationdirect C0-12dd1e-D Firmware, Automationdirect C0-12dd2e-1-D Firmware, Automationdirect C0-12dd2e-2-D Firmware, Automationdirect C0-12dd2e-D Firmware, Automationdirect C0-12dre-1-D Firmware, Automationdirect C0-12dre-2-D Firmware, Automationdirect C0-12dre-D Firmware.

## How do I fix CVE-2021-32982?

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

## Is CVE-2021-32982 being exploited?

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

## Other vulnerabilities in Automation Direct CLICK PLC CPU Modules: C0-1x CPUs

- [CVE-2021-32980](https://insights.sbomify.com/CVE-2021-32980/): Automation Direct CLICK PLC CPU Modules Authentication Bypass Using an Alternate Path or Channel (critical 9.8)
- [CVE-2021-32984](https://insights.sbomify.com/CVE-2021-32984/): Automation Direct CLICK PLC CPU Modules Authentication Bypass Using an Alternate Path or Channel (critical 9.8)
- [CVE-2021-32986](https://insights.sbomify.com/CVE-2021-32986/): Automation Direct CLICK PLC CPU Modules Authentication Bypass Using an Alternate Path or Channel (critical 9.8)
- [CVE-2021-32978](https://insights.sbomify.com/CVE-2021-32978/): Automation Direct CLICK PLC CPU Modules Plaintext Storage of a Password (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32982 and fix it if it is affected.

What it is: CVE-2021-32982 is a high-severity vulnerability in Automation Direct CLICK PLC CPU Modules: C0-1x CPUs, published on 4 Apr 2022. 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-2021-32982 in the wild and no public exploit code.

Affected product: Automation Direct CLICK PLC CPU Modules: C0-1x CPUs. 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-2021-32982/ (Markdown: https://insights.sbomify.com/CVE-2021-32982/index.md)
```

## Sources

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

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