AutomationDirect DirectLOGIC with Ethernet Communication Uncontrolled Resource Consumption
AutomationDirect DirectLOGIC is vulnerable to a a specially crafted packet can be sent continuously to the PLC to prevent access from DirectSoft and other devices, causing a denial-of-service condition. 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;
- Published
- Aug 31, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 61th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · icscert
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| automationdirect | d0-06dd1 firmware | cpe:2.3:o:automationdirect:d0-06dd1_firmware |
| automationdirect | d0-06dd1 | cpe:2.3:h:automationdirect:d0-06dd1 |
| automationdirect | d0-06dd2 firmware | cpe:2.3:o:automationdirect:d0-06dd2_firmware |
| automationdirect | d0-06dd2 | cpe:2.3:h:automationdirect:d0-06dd2 |
| automationdirect | d0-06dr firmware | cpe:2.3:o:automationdirect:d0-06dr_firmware |
| automationdirect | d0-06dr | cpe:2.3:h:automationdirect:d0-06dr |
| automationdirect | d0-06da firmware | cpe:2.3:o:automationdirect:d0-06da_firmware |
| automationdirect | d0-06da | cpe:2.3:h:automationdirect:d0-06da |
| automationdirect | d0-06ar firmware | cpe:2.3:o:automationdirect:d0-06ar_firmware |
| automationdirect | d0-06ar | cpe:2.3:h:automationdirect:d0-06ar |
| automationdirect | d0-06aa firmware | cpe:2.3:o:automationdirect:d0-06aa_firmware |
| automationdirect | d0-06aa | cpe:2.3:h:automationdirect:d0-06aa |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- automationdirect d0-06aa firmwarebefore 2.72
- automationdirect d0-06ar firmwarebefore 2.72
- automationdirect d0-06da firmwarebefore 2.72
- automationdirect d0-06dd1 firmwarebefore 2.72
- automationdirect d0-06dd1-d firmwarebefore 2.72
- automationdirect d0-06dd2 firmwarebefore 2.72
- automationdirect d0-06dd2-d firmwarebefore 2.72
- automationdirect d0-06dr firmwarebefore 2.72
- automationdirect d0-06dr-d firmwarebefore 2.72
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
AutomationDirect DirectLOGIC D0-06 series CPUs
- D0-06DD1 and later · before 2.72affected
- D0-06DD2 and later · before 2.72affected
- D0-06DR and later · before 2.72affected
- D0-06DA and later · before 2.72affected
- D0-06AR and later · before 2.72affected
- D0-06AA and later · before 2.72affected
- D0-06DD1-D and later · before 2.72affected
- D0-06DD2-D and later · before 2.72affected
- D0-06DR-D and later · before 2.72affected
Same product
automationdirect: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-2003AutomationDirect DirectLOGIC with Serial Communication Cleartext Transmission36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sam HansonDragos
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.