CVE-2023-43820
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 wLogTitlesPrevValueLen 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 wLogTitlesPrevValueLen field of DPS project files. By crafting a DPS file with an oversized value in this length field, an attacker can overflow a fixed-size stack buffer and overwrite return addresses or adjacent variables, achieving arbitrary code execution when the victim opens the malicious file.
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.
-
Identify installed DOPSoft versionOpen Windows Control Panel > Programs and Features, or right-click the DOPSoft executable (typically in C:\Program Files\Delta Electronics\DOPSoft or similar) and select Properties > Details to view the File VersionAffected if The displayed version falls within 2.00.00.00 through 2.00.07.04 (inclusive)
-
Locate DOPSoft executable pathSearch for dopsoft.exe using Windows Explorer search or command: dir /s /b C:\dopsoft.exe 2>nulAffected if DOPSoft is found at any installation path and its version is in the affected range
-
Review recent DPS project filesCheck Downloads folder, email attachments, and recent documents for .dps files: dir %USERPROFILE%\Downloads\*.dps /a /t:c 2>nulAffected if Untrusted or unknown-origin DPS files exist on the system and DOPSoft version is vulnerable
-
Check default file association for DPS filesRight-click any .dps file > Properties > Opens with, or check HKEY_CLASSES_ROOT\.dps registry key to confirm DOPSoft is the default handlerAffected if DPS files are associated with DOPSoft version in the affected range
Environment is affected if DOPSoft version 2.00.00.00 through 2.00.07.04 is installed and can open DPS project files, particularly from untrusted sources.
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 dataUsers should not open DPS files from untrusted or unknown sources. Organizations should implement email/web gateway filtering for DPS attachments and consider application whitelisting to block DOPSoft from loading untrusted project files until an official patch is available from Delta Electronics.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43820 — 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-43820 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