CVE-2020-7002
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 · uneditedDelta Industrial Automation CNCSoft ScreenEditor, v1.00.96 and prior. Multiple stack-based buffer overflows can be exploited when a valid user opens a specially crafted, malicious input file.
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 · moderate confidenceMultiple stack-based buffer overflow vulnerabilities exist in Delta Industrial Automation CNCSoft ScreenEditor v1.00.96 and prior. When a user opens a specially crafted malicious input file (likely .screenproj project files), the application fails to properly validate input bounds before copying data to fixed-size stack buffers, leading to memory corruption and potential arbitrary 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<= 1.00.96CVSS 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.
-
Locate CNCSoft ScreenEditor installationSearch for 'CNCSoft' or 'ScreenEditor' in Program Files directories, or check the application executable file location. Common paths include C:\Program Files\Delta Industrial Automation\CNCSoft\ScreenEditor or similar.Affected if The application is found installed on the system
-
Identify installed versionRight-click the ScreenEditor executable (usually named ScreenEditor.exe or similar), select Properties, and check the File Version field under the Details tab. Alternatively, right-click and select 'View' > 'Details' in File Explorer.Affected if The version displayed is 1.00.96 or lower (e.g., 1.00.96, 1.00.95, 1.00.90, etc.)
-
Compare against affected version rangeCompare your identified version number to the affected range: any version less than or equal to 1.00.96 is vulnerable. Versions above 1.00.96 are not affected by this specific CVE.Affected if The installed version is 1.00.96 or any prior version (1.00.x where x is 96 or lower)
-
Check for .screenproj file associationLook for .screenproj file type associations in Windows: open Default Apps in Windows Settings, or check HKEY_CLASSES_ROOT\.screenproj in the Registry Editor. Also check if recent .screenproj files exist in user directories.Affected if The system has .screenproj file associations configured or contains .screenproj project files, indicating the vulnerable application is actively used
A system is affected if CNCSoft ScreenEditor version 1.00.96 or any lower version is installed and the system handles .screenproj project files.
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 or unknown ScreenEditor project files; obtain and apply any vendor patches or updated versions when released; consider running the application in an isolated environment to limit impact if exploitation occurs.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7002 — 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-2020-7002 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