CVE-2023-43821
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stack based buffer overflow exists in Delta Electronics Delta Industrial Automation DOPSoft when parsing the wLogTitlesActionLen field of a DPS file. A remote, unauthenticated attacker can exploit this vulnerability by enticing a user to open a specially crafted DPS file to achieve remote code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack-based buffer overflow exists in Delta Electronics DOPSoft when parsing the wLogTitlesActionLen field of DPS files. An attacker can exploit this by crafting a malicious DPS file that triggers overflow during parsing, achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.00.00.00, <= 2.00.07.04CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if DOPSoft is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for 'DOPSoft' or 'Deltaww' entries.Affected if DOPSoft or Deltaww DOPSoft appears in the installed programs list
-
Verify the installed version against affected rangeIf DOPSoft is found, note the DisplayVersion from the uninstall list or check the executable version by right-clicking the main DOPSoft .exe file (typically in Program Files or Program Files (x86)), selecting Properties, and viewing the Details tab.Affected if The installed version is 2.00.00.00 through 2.00.07.04 inclusive
-
Check for DPS file associationsOpen File Explorer, search for .DPS files on the system, or check the registry under HKCR\.dps to see if DOPSoft is registered as the handler for .DPS files.Affected if DOPSoft is associated with .DPS file extension and the software is installed in an affected version
-
Review recent DPS file activityOpen Windows Event Viewer and search for recent file access events involving .DPS files, or check the application's recent files list if accessible. You can also use PowerShell: Get-ChildItem -Path $env:USERPROFILE -Recurse -Filter *.dps -ErrorAction SilentlyContinue | Select-Object FullName, LastWriteTimeAffected if Any .DPS files exist on the system that were opened by DOPSoft, especially from untrusted sources
The system is affected if DOPSoft version 2.00.00.00 through 2.00.07.04 is installed and configured to handle DPS files, as the vulnerability triggers when parsing the wLogTitlesActionLen field of a malicious DPS file.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDo not open untrusted DPS files from unverified sources. Apply vendor patches when available. Consider network isolation for systems running DOPSoft.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43821 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-43821 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data