CVE Tools
Track your stack

CVE-2022-2003

AutomationDirect DirectLOGIC with Serial Communication Cleartext Transmission

No known exploitation. EPSS puts it in the 55th percentile. Fixed in 2.72.

CVSS 3.17.7HighEPSS percentile55th0.8% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix2.72Upgrade to this build

Published Updated Sources: CVE.org, NVD, BDU, CSAF

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • AutomationDirect DirectLOGIC D0-06 series CPUsAffected: ≥ D0-06DD1, < 2.72Upgrade to: 2.72Affected: ≥ D0-06DD2, < 2.72Upgrade to: 2.72Affected: ≥ D0-06DR, < 2.72Upgrade to: 2.72Affected: ≥ D0-06DA, < 2.72Upgrade to: 2.72 + 5 more branchesStated by: CVE record
  • Automationdirect D0-06dd1 FirmwareAffected: < 2.72Upgrade to: 2.72Stated by: NVD
  • Automationdirect D0-06dd2 FirmwareAffected: < 2.72Upgrade to: 2.72Stated by: NVD
  • Automationdirect D0-06dr FirmwareAffected: < 2.72Upgrade to: 2.72Stated by: NVD
  • Automationdirect D0-06da FirmwareAffected: < 2.72Upgrade to: 2.72Stated by: NVD

Versions as the sources state them. 7 more products have version data. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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;

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS55th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.8% chance of exploitation activity in the next 30 days, which ranks it in the 55th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 813 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

And 4 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Scored 7.7 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 9 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for H0-ECOM, not every advisory.