CVE-2023-51587
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 · uneditedVoltronic Power ViewPower getModbusPassword Missing Authentication Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Voltronic Power ViewPower. Authentication is not required to exploit this vulnerability. The specific flaw exists within the getModbusPassword method. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-22073.
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 confidenceThis vulnerability in Voltronic Power ViewPower exposes the getModbusPassword method without requiring any authentication, allowing remote attackers to retrieve stored credentials. The lack of authentication check before the getModbusPassword function directly discloses sensitive password data that could be used for further unauthorized access to the system.
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= 1.04.21353CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ViewPower installationLocate the ViewPower installation directory, typically found under C:\Program Files\ViewPower or C:\Program Files (x86)\ViewPower on Windows systems. Check for the presence of ViewPower service or application files.Affected if ViewPower software is installed on the system
-
Verify installed versionLocate the version information in the installation directory, typically in a version.txt file, or right-click on the main executable (ViewPower.exe) and select Properties > Details to view the File Version.Affected if The installed version is exactly 1.04.21353
-
Check if web interface is exposedIdentify if the ViewPower web management service (typically running on ports 8080, 8090, or 80/443) is accessible from the network. Use netstat or similar tools to identify listening ports and test remote connectivity.Affected if The ViewPower web interface is accessible from network locations
-
Test getModbusPassword endpoint authenticationAttempt to access the getModbusPassword method via HTTP request (e.g., http://<server>:<port>/getModbusPassword or similar endpoint) without providing credentials. If the endpoint returns password data without requiring authentication, the vulnerability is present.Affected if The getModbusPassword endpoint returns sensitive data without requiring authentication credentials
A system is affected if Voltronic Power ViewPower version 1.04.21353 is installed with its web interface exposed and the getModbusPassword endpoint responds without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authentication and authorization checks on the getModbusPassword method and restrict access to credential-related functions. Consider network segmentation to limit exposure of the management interface while awaiting vendor patch.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-51587 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51587 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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