dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51570

CRITICAL · 9.8 CVSS v3.0 Published 2024-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Voltronic Power ViewPower Pro Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Voltronic Power ViewPower Pro. Authentication is not required to exploit this vulnerability. The specific flaw exists within the RMI interface, which listens on TCP port 41009 by default. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-21012.

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

Deserialization vulnerability in ViewPower Pro's RMI service on TCP port 41000 allows unauthenticated remote attackers to execute arbitrary code as SYSTEM due to lack of validation on user-supplied serialized Java data.

MitigationRestrict network access to port 41009 via firewall or disable the RMI service if not required; apply vendor patch when available.

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
ViewpowerApplication
Affected:= 2.0-22165

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.0/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 ViewPower software is installed
    Check for ViewPower installation directories (commonly C:\Program Files\ViewPower or C:\ViewPower) or look for ViewPower in Add/Remove Programs. On Linux check /usr/local/viewpower or similar paths.
    Affected if ViewPower software is present on the system
  2. Identify installed ViewPower version
    Locate version information in installation files, typically in a version.txt, about dialog, or the executable properties. Common paths: C:\Program Files\ViewPower\ViewPower.exe or check the service executable.
    Affected if Version equals 2.0-22165 exactly or falls within the 2.0-22165 release line
  3. Confirm RMI service is listening
    Run netstat -an | findstr "41000" or use PowerShell: Get-NetTCPConnection -LocalPort 41000 to check if port 41000 is in LISTEN state. Note: Some documentation references port 41009 for RMI.
    Affected if Port 41000 (or 41009) is open and listening for connections
  4. Verify network exposure of RMI service
    Check if the RMI service binds to 0.0.0.0 or an external interface rather than 127.0.0.1 localhost. Use nmap -sV -p 41000 <target> or verify the binding address in service configuration.
    Affected if Service accepts remote connections on non-localhost addresses
  5. Check RMI authentication status
    Review ViewPower service configuration files for RMI authentication settings. Attempt a test connection to the RMI port using a tool like jmxterm or check if authentication is required in the service config.
    Affected if RMI service permits unauthenticated connections (no authentication enforced)

User is affected if ViewPower version 2.0-22165 is installed AND the RMI service on port 41000/41009 is exposed to the network without authentication enforcement.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to port 41009 via firewall or disable the RMI service if not required; apply vendor patch when available.

Fix this in Viewpower Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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