# CVE-2022-2003: AutomationDirect DirectLOGIC with Serial Communication Cleartext Transmission

> A crafted serial message causes the PLC to leak its password in cleartext, enabling unauthorized access and modification.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-cwvq-v3mj-c66c

## What is CVE-2022-2003?

CVE-2022-2003 is a high-severity vulnerability in AutomationDirect DirectLOGIC D0-06 series CPUs, published on 31 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AutomationDirect DirectLOGIC is vulnerable to a specifically crafted serial message to the CPU serial port that will cause the PLC to respond with the PLC password in cleartext. This could allow an attacker to access and make unauthorized changes. This issue affects: AutomationDirect DirectLOGIC D0-06 series CPUs D0-06DD1 versions prior to 2.72; D0-06DD2 versions prior to 2.72; D0-06DR versions prior to 2.72; D0-06DA versions prior to 2.72; D0-06AR versions prior to 2.72; D0-06AA versions prior to 2.72; D0-06DD1-D versions prior to 2.72; D0-06DD2-D versions prior to 2.72; D0-06DR-D versions prior to 2.72;

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

## Which versions are affected by CVE-2022-2003?

It affects 9 products.


Products: Automationdirect D0-06aa Firmware, Automationdirect D0-06ar Firmware, Automationdirect D0-06da Firmware, Automationdirect D0-06dd1-D Firmware, Automationdirect D0-06dd1 Firmware, Automationdirect D0-06dd2-D Firmware, Automationdirect D0-06dd2 Firmware, Automationdirect D0-06dr-D Firmware, Automationdirect D0-06dr Firmware.

## How do I fix CVE-2022-2003?

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

## Is CVE-2022-2003 being exploited?

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

## Other vulnerabilities in AutomationDirect DirectLOGIC D0-06 series CPUs

- [CVE-2022-2004](https://insights.sbomify.com/CVE-2022-2004/): AutomationDirect DirectLOGIC with Ethernet Communication Uncontrolled Resource Consumption (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2003 and fix it if it is affected.

What it is: CVE-2022-2003 is a high-severity vulnerability in AutomationDirect DirectLOGIC D0-06 series CPUs, published on 31 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2003 in the wild and no public exploit code.

Affected product: AutomationDirect DirectLOGIC D0-06 series 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-2022-2003/ (Markdown: https://insights.sbomify.com/CVE-2022-2003/index.md)
```

## Sources

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

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