CVE-2020-27287
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 Electronics CNCSoft-B Versions 1.0.0.2 and prior is vulnerable to an out-of-bounds write while processing project files, which may allow an attacker to execute arbitrary code.
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 confidenceDelta Electronics CNCSoft-B versions 1.0.0.2 and prior contains an out-of-bounds write vulnerability in project file processing. An attacker can craft a malicious project file that triggers a buffer overflow, allowing arbitrary code execution on the targeted system.
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.0.0.2CVSS 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 if Delta CNCSoft-B is installedCheck Program Files or Program Files (x86) for 'CNCSoft' or 'Delta' folders, or search for 'CNCSoft' in Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if CNCSoft-B folder exists on the system
-
Determine installed version of CNCSoft-BRight-click the CNCSoft-B executable, select Properties, then view the Details tab for Product Version; alternatively check Add/Remove Programs for the version listedAffected if Version is 1.0.0.2 or lower, or no version number is displayed (indicating unpatched early release)
-
Confirm project file functionality is presentLaunch CNCSoft-B and verify if the application supports opening or importing project files (look for File > Open, File > Import, or file types like .cnc, .proj, .gcode in the open dialog)Affected if The application has file open/import capability and can process project files
-
Check for untrusted project file handlingReview system logs or user workflow documents to determine whether the software is used to open project files from external or untrusted sourcesAffected if Users routinely open project files from outside the organization or from untrusted sources
A system is affected if Delta CNCSoft-B version 1.0.0.2 or prior is installed and the software is used to open or import project files, since the vulnerability is triggered during project file processing.
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 dataApply vendor patches when available; avoid opening untrusted project files; restrict file import functionality to trusted sources; implement application sandboxing and least-privilege execution.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27287 — 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-27287 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