dbcve.org
Softpac ProjectApplication · Opto22

CVE-2020-10612

CRITICAL · 9.1 CVSS v3.1 Published 2020-05-14
Fix available
A fix is available. Upgrade to after 9.6 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
Opto 22 SoftPAC Project Version 9.6 and prior. SoftPACAgent communicates with SoftPACMonitor over network Port 22000. However, this port is open without any restrictions. This allows an attacker with network access to control the SoftPACAgent service including updating SoftPAC firmware, starting or stopping service, or writing to certain registry values.

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

Opto 22 SoftPAC Project versions 9.6 and prior expose network port 22000 used for SoftPACAgent-to-SoftPACMonitor communication without any authentication or access restrictions. An unauthenticated attacker with network access can remotely control the SoftPACAgent service, including updating firmware, starting/stopping services, and modifying certain registry values.

MitigationRestrict network access to port 22000 through firewall rules, network segmentation, or VPN access controls to limit communication to only authorized SoftPACMonitor instances.

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
Softpac ProjectApplication
Affected:<= 9.6

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check if SoftPAC Project is installed
    Look for SoftPAC installation directories (commonly C:\Program Files\Opto22\SoftPAC or C:\Opto22\SoftPAC) or check Windows Services for 'SoftPACAgent' or 'SoftPACMonitor' services
    Affected if SoftPAC Project software is present on the system
  2. Determine installed SoftPAC version
    Check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Opto22\SoftPAC for a Version value, or right-click the SoftPAC.exe file in the installation folder and view Properties > Details
    Affected if The version number is 9.6 or lower
  3. Verify if port 22000 is listening
    Run command 'netstat -an | findstr :22000' or use PowerShell 'Get-NetTCPConnection -LocalPort 22000' to check if the SoftPACAgent port is bound and listening
    Affected if Port 22000 shows as LISTENING or ESTABLISHED
  4. Test port accessibility from untrusted network
    From a remote system, attempt to connect to port 22000 using telnet, nc, or PowerShell Test-NetConnection -Port 22000 -ComputerName <target>
    Affected if The connection succeeds, indicating the port is externally accessible
  5. Check firewall rules allowing unrestricted port 22000 access
    Run 'netsh advfirewall firewall show rule name=all' or inspect Windows Firewall inbound rules for rules allowing port 22000 from any source IP
    Affected if An inbound rule exists for port 22000 that permits traffic from non-authorized IP addresses

A system is affected if SoftPAC Project version 9.6 or lower is installed AND port 22000 is listening and accessible from networks that should not have unrestricted access to this service.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 9.6
Interim mitigation

Restrict network access to port 22000 through firewall rules, network segmentation, or VPN access controls to limit communication to only authorized SoftPACMonitor instances.

Recommended fix Moderate confidence

SoftPAC Project version > 9.6 (contact Opto 22 for specific fixed release)

  1. Upgrade SoftPAC Project to a version newer than 9.6 that includes the security fix
  2. After upgrading, verify that network access to port 22000 is restricted through firewall rules or network segmentation
  3. Configure access control lists (ACLs) to allow only trusted IP addresses to communicate with port 22000
  4. Test the deployment to confirm the vulnerability is resolved and legitimate operations still function properly
Caveat Review release notes for any compatibility changes or configuration requirements in newer versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Softpac Project Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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