dbcve.org
IspsoftApplication · Deltaww

CVE-2020-27280

HIGH · 7.8 CVSS v3.1 Published 2021-01-26
Fix available
A fix is available. Upgrade to after 3.12 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
A use after free issue has been identified in the way ISPSoft(v3.12 and prior) processes project files, allowing an attacker to craft a special project file that may allow arbitrary code execution.

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 confidence

A use-after-free vulnerability exists in ISPSoft v3.12 and prior versions when processing project files. An attacker can craft a malicious project file that, when opened by a victim, triggers a use-after-free condition allowing arbitrary code execution with the privileges of the running user.

MitigationUpdate ISPSoft to a version newer than v3.12 when available. Avoid opening untrusted or unverified project files from untrusted sources. Apply the principle of least privilege for users running ISPSoft.

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
IspsoftApplication
Affected:<= 3.12

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. Identify if ISPSoft is installed
    Check for ISPSoft installation directory, typically in Program Files (x86)\Delta Industrial Automation\ISPSoft, or search for ISPSoft.exe on the system
    Affected if ISPSoft is found on the system
  2. Determine installed ISPSoft version
    Right-click on ISPSoft.exe, select Properties, then view the Details tab for version information, or launch ISPSoft and check Help > About
    Affected if Version is 3.12 or lower (any version up to and including 3.12)
  3. Verify project file handling context
    Understand that the vulnerability triggers specifically when ISPSoft opens a project file - check recent or incoming project files (.isp or related formats) from external sources
    Affected if Users open project files from untrusted or unverified sources in ISPSoft v3.12 or prior

If ISPSoft version 3.12 or lower is installed and users open project files, the environment is potentially affected by this use-after-free vulnerability.

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 3.12
Interim mitigation

Update ISPSoft to a version newer than v3.12 when available. Avoid opening untrusted or unverified project files from untrusted sources. Apply the principle of least privilege for users running ISPSoft.

Fix this in Ispsoft Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-27280 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