Cncsoft BApplication · Deltaww

CVE-2020-27291

HIGH · 7.8 CVSS v3.1 Published 2021-01-11
Fix available
A fix is available. Upgrade to after 1.0.0.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Delta Electronics CNCSoft-B Versions 1.0.0.2 and prior is vulnerable to an out-of-bounds read 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 confidence

Delta Electronics CNCSoft-B versions 1.0.0.2 and prior contain an out-of-bounds read vulnerability when parsing project files. The vulnerability occurs due to insufficient bounds checking during file processing, which can lead to memory corruption and potentially allow arbitrary code execution by a specially crafted project file.

MitigationUpdate to a patched version of CNCSoft-B when available from the vendor. Until then, avoid opening untrusted or unverified project files and restrict network exposure of systems running this software.

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
Cncsoft BApplication
Affected:<= 1.0.0.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate CNCSoft-B installation
    Search for 'CNCSoft-B' or 'cncsoft' in Program Files directories, or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Delta Electronics software entries
    Affected if The software is found installed on the system
  2. Retrieve installed version
    Right-click the CNCSoft-B executable (typically named CNCSoft-B.exe or similar), select Properties, and check the Details tab for the File Version or Product Version
    Affected if The version displayed is 1.0.0.2 or any version lower than 1.0.0.2
  3. Confirm version matches affected range
    Compare the retrieved version number against the affected range: any version <= 1.0.0.2 is vulnerable
    Affected if The installed version is 1.0.0.2 or prior
  4. Verify project file functionality is in use
    CNCSoft-B is a CNC programming tool that parses project files as its core function; confirm whether users have opened or create project files (.cnp, .cnc, or vendor-specific formats) with this software
    Affected if The software is used to open or create project files (which is the default use case for this application)

The system is affected if CNCSoft-B is installed with version 1.0.0.2 or any prior version, and the software is used to process project files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.0.2
Interim mitigation

Update to a patched version of CNCSoft-B when available from the vendor. Until then, avoid opening untrusted or unverified project files and restrict network exposure of systems running this software.

Fix this in Cncsoft B Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27291 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-27291 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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