basicsecurity.net
Proof, not just disclosure.
Threats / Delta Electronics / CVE-2021-38406
CVE-2021-38406 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Delta Electronics DOPSoft 2 vulnerability

Delta Electronics DOPSoft 2 contains an out-of-bounds write vulnerability in project file parsing due to improper input validation, enabling arbitrary code execution.

Verdict

Today item — known-exploited.

An unauthenticated attacker can craft a malicious project file to trigger an out-of-bounds write in DOPSoft 2, achieving code execution on the affected system. This vulnerability has been exploited in the wild.

CISA KEV Yes · 2022-08-253EPSS 0.77892 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-08-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.77892 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: Delta Electronics, DOPSoft 2. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious DOPSoft 2 project file with specially formatted data that bypasses input validation checks.
Business
Engineering and manufacturing operations relying on DOPSoft 2 for industrial control system configuration face direct compromise risk.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I deliver the malicious project file to a target user via email, file sharing, or compromised repository.
Business
Operational technology environments become vulnerable to supply chain and social engineering attack vectors.
3

Lateral reach — past segmentation narrative 3

Attacker
I trigger the vulnerability when the user opens the project file in DOPSoft 2, causing an out-of-bounds write that overwrites memory.
Business
Arbitrary code execution on engineering workstations enables lateral movement into critical manufacturing and power systems.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by icscert (CNA)
  • Named finder/reporter credit (CVE.org)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
    • Disclosure & credit2
    Catalogued by icscertCNA
    Credited with finding itkimiya, working with Trend Micro’s Zero Day Initiativeunspecified