Code execution via malformed project-file parsing
Published Sep 17, 2021 · Updated Apr 23, 2025
Heap-based buffer overflow in Delta Electronics DOPSoft 2 2.00.07 and earlier allows attackers to execute code via a crafted project file. The project-file parser fails to validate user-supplied data before writing it into a heap buffer, allowing data to overrun the allocation. Exploitation requires a user to open the file, and code runs with the privileges of the DOPSoft process.
Summary
What happened
Heap-based buffer overflow in Delta Electronics DOPSoft 2 2.00.07 and earlier allows attackers to execute code via a crafted project file. The project-file parser fails to validate user-supplied data before writing it into a heap buffer, allowing data to overrun the allocation. Exploitation requires a user to open the file, and code runs with the privileges of the DOPSoft process.
The record
- CVE
- CVE-2021-38404
- Published
- Sep 17, 2021
- Updated
- Apr 23, 2025
- Vendor
- Delta Electronics, Inc.
- Product
- DOPSoft 2
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2021CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=2.00.07
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo