Vision ProApplication · Netop

CVE-2021-27193

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-25
Fix available
A fix is available. Upgrade to after 9.7.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Incorrect default permissions vulnerability in the API of Netop Vision Pro up to and including 9.7.1 allows a remote unauthenticated attacker to read and write files on the remote machine with system privileges resulting in a privilege escalation.

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

Netop Vision Pro versions up to 9.7.1 contain an API with insecure default permissions that allows any remote unauthenticated attacker to interact with the API and perform privileged file operations. This grants the attacker SYSTEM-level access to read and write arbitrary files on the target machine, effectively enabling complete remote code execution and privilege escalation.

MitigationUpgrade Netop Vision Pro to the latest version beyond 9.7.1 which contains the corrected default permissions. If immediate patching is not feasible, restrict network exposure of the Vision Pro API to trusted networks and implement additional access controls.

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
Vision ProApplication
Affected:<= 9.7.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify Netop Vision Pro is installed
    Check for Netop Vision Pro in the list of installed programs. On Windows, open Control Panel > Programs and Features, or run: reg query 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall' /s | findstr -i 'Netop Vision'
    Affected if Netop Vision Pro appears in installed programs list
  2. Determine the installed version
    Open the Vision Pro application and navigate to Help > About, or check the executable properties: right-click the Vision Pro executable (typically in C:\Program Files\Netop\Vision Pro\) and view Version info
    Affected if Version number is 9.7.1 or lower (any version up to and including 9.7.1)
  3. Verify the Vision API service is enabled
    Open Windows Services (services.msc) and look for Netop Vision services, or check for the Vision API process listening on typical ports (TCP 20020-20021 or similar). Run: netstat -an | findstr '200'
    Affected if The Netop Vision API service is running and accepting connections
  4. Check network exposure of the Vision API
    Run: netstat -an | findstr 'LISTENING' to identify ports the Vision API binds to, then verify if these ports are exposed externally or accessible from untrusted networks
    Affected if The API ports are bound to 0.0.0.0 (all interfaces) or are accessible from outside trusted network segments

A system is affected if Netop Vision Pro version 9.7.1 or lower is installed with the vulnerable API component enabled and network-accessible.

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

Upgrade Netop Vision Pro to the latest version beyond 9.7.1 which contains the corrected default permissions. If immediate patching is not feasible, restrict network exposure of the Vision Pro API to trusted networks and implement additional access controls.

Fix this in Vision Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27193 — 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-2021-27193 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