dbcve.org
Clusterpro XApplication · Nec

CVE-2021-20707

HIGH · 7.5 CVSS v3.1 Published 2021-11-03
Fix available
A fix is available. Upgrade to after 4.3 or later.
See remediation →
84/100
Remediation priority · High
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
Improper input validation vulnerability in the Transaction Server CLUSTERPRO X 4.3 for Windows and earlier, EXPRESSCLUSTER X 4.3 for Windows and earlier, CLUSTERPRO X 4.3 SingleServerSafe for Windows and earlier, EXPRESSCLUSTER X 4.3 SingleServerSafe for Windows and earlier allows attacker to read files upload via network..

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

Improper input validation in the Transaction Server component of CLUSTERPRO X and EXPRESSCLUSTER X 4.3 for Windows allows remote attackers to read arbitrary files via network upload due to insufficient validation of user-supplied input.

MitigationApply vendor patches or upgrade to a version newer than 4.3 for Windows. Additionally, implement network segmentation and restrict network access to the Transaction Server to limit attack surface.

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
Clusterpro XApplication
Affected:>= 1.0, <= 4.3
Clusterpro X SingleserversafeApplication
Affected:>= 1.0, <= 4.3
Expresscluster XApplication
Affected:>= 1.0, <= 4.3
Expresscluster X SingleserversafeApplication
Affected:>= 1.0, <= 4.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 the installed Clusterpro or Expresscluster product
    Check the installed software list in Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' in PowerShell for registry keys under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
    Affected if The product name contains 'Clusterpro X', 'Clusterpro X Singleserversafe', 'Expresscluster X', or 'Expresscluster X Singleserversafe' and the version is 4.3 or lower
  2. Determine the installed version number
    Run 'clpclt -v' or 'clpversion' from the Clusterpro/Expresscluster bin directory, or inspect the version field in the Windows registry under the product's uninstall key
    Affected if The version is 4.3 or any version from 1.0 up to and including 4.3
  3. Verify the Transaction Server component is enabled
    Open Clusterpro/Expresscluster Cluster Manager, navigate to the server properties, and check the Transaction Server service status. Alternatively, check if the 'clptxsv' or 'Transaction Server' service is running via 'services.msc'
    Affected if The Transaction Server service (clptxsv) is installed and running on the Windows host
  4. Confirm network exposure of the Transaction Server
    Check the firewall rules and network binding configuration for ports used by the Transaction Server (typically TCP ports 29001-29010 or custom configured ports). Use 'netstat -an' or check Windows Firewall inbound rules
    Affected if The Transaction Server port is open to untrusted network access, allowing remote attackers to send network upload requests

The environment is affected if any Clusterpro X or Expresscluster X product version 4.3 or earlier is installed on Windows with the Transaction Server component enabled and exposed to the network.

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

Apply vendor patches or upgrade to a version newer than 4.3 for Windows. Additionally, implement network segmentation and restrict network access to the Transaction Server to limit attack surface.

Recommended fix Moderate confidence

Version 4.3.1 or later (contact NEC for exact fixed release)

  1. 1. Identify the exact current version of Clusterpro X or Expresscluster X installed by checking the product's version information in Windows Control Panel or the product's management interface.
  2. 2. Contact NEC technical support or visit the official NEC security advisory page at jpn.nec.com to obtain the specific patch or upgrade version that addresses CVE-2021-20707.
  3. 3. Before applying any update, review the release notes for version 4.3.1 or later (depending on NEC's official fix) to understand any compatibility requirements or known issues.
  4. 4. Create a full backup of the current Clusterpro/Expresscluster configuration.
  5. 5. Apply the vendor-provided update following NEC's official installation instructions for your specific product variant (Clusterpro X, Clusterpro X SingleServerSafe, Expresscluster X, or Expresscluster X SingleServerSafe).
  6. 6. After upgrade, verify that the Transaction Server component is functioning correctly and that file upload operations work as expected.
Caveat Review release notes for any configuration changes or compatibility considerations before upgrading

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

Fix this in Clusterpro X Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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