CVE-2020-27289
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 has a null pointer dereference issue 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 · moderate confidenceDelta Electronics CNCSoft-B versions 1.0.0.2 and prior contains a null pointer dereference vulnerability triggered when processing malicious project files. An attacker can craft a specially formatted project file that causes the application to dereference a null pointer during parsing, potentially leading to arbitrary code execution with the privileges of the affected application.
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.
-
Check if CNCSoft-B is installedSearch for the CNCSoft-B installation directory, typically under 'C:\Program Files\Delta Electronics\CNCSoft-B' or check Windows Registry under 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall' for an entry containing 'CNCSoft' or 'Delta'Affected if CNCSoft-B is found on the system
-
Identify the installed versionLocate the main executable (typically 'CNCSoft.exe' or similar) in the installation directory, right-click and select Properties, then check the 'Details' tab for the File Version, or query the registry uninstall key for the DisplayVersion valueAffected if The version displayed is 1.0.0.2 or earlier
-
Compare version to affected rangeCompare the found version number against the affected range: all versions <= 1.0.0.2 are vulnerableAffected if The installed version is 1.0.0.2 or any earlier version number
-
Confirm project file usageThe vulnerability is triggered when the application parses project files (typically .vcp, .prj, or CNC-specific project file formats). Verify if the software is used to open or create project filesAffected if The software is used to open project files, which is the normal and default operation of the application
A system is affected if CNCSoft-B version 1.0.0.2 or earlier is installed and the application is used to process project files, which is its primary function.
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 avoid opening untrusted project files in CNCSoft-B until a vendor patch is available. Contact Delta Electronics for available security updates and consider applying defense-in-depth controls such as restricting file handling permissions.
- Consultation3.0 h
- Implementation8.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 $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27289 — 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-27289 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