ViewpowerApplication · Voltronicpower

CVE-2023-51574

CRITICAL · 9.8 CVSS v3.0 Published 2024-05-03
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 updateManagerPassword Exposed Dangerous Method Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of Voltronic Power ViewPower. Authentication is not required to exploit this vulnerability. The specific flaw exists within the updateManagerPassword method. The issue results from the exposure of a dangerous function. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-22010.

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

The vulnerability exists in Voltronic Power ViewPower's updateManagerPassword method, which is exposed without authentication. An attacker can call this dangerous function directly to bypass authentication and potentially modify administrator credentials, gaining full system access. This is a direct authentication bypass via exposed administrative functionality.

MitigationRestrict network access to ViewPower interfaces, implement proper authentication enforcement on the updateManagerPassword method, and contact Voltronic Power for vendor-supplied patches. If no patch exists, consider compensating controls such as network segmentation and monitoring for unauthorized password change attempts.

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:= 1.04.21353

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. Confirm ViewPower installation
    Identify if Voltronic Power ViewPower software is installed on the system. Check program files, running services, or listening network ports associated with ViewPower (typically uses port 8080 or 9000 for web interface).
    Affected if ViewPower software is installed and running.
  2. Check installed version
    Locate the ViewPower version information. This is typically found in the software itself, About section, or version file within the ViewPower installation directory. Compare your installed version to 1.04.21353.
    Affected if Installed version is exactly 1.04.21353.
  3. Verify web interface exposure
    Determine if the ViewPower web interface is accessible over the network. Attempt to access the login page from an external host or check firewall rules allowing inbound access to ViewPower ports.
    Affected if The ViewPower web interface is reachable from untrusted networks.
  4. Test updateManagerPassword accessibility
    Send a direct HTTP request to the updateManagerPassword method endpoint. This typically involves a POST request to the web interface without providing authentication credentials.
    Affected if The updateManagerPassword method responds to unauthenticated requests.

A system is affected if ViewPower version 1.04.21353 is installed and the updateManagerPassword method is accessible without authentication, allowing credential modification.

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 ViewPower interfaces, implement proper authentication enforcement on the updateManagerPassword method, and contact Voltronic Power for vendor-supplied patches. If no patch exists, consider compensating controls such as network segmentation and monitoring for unauthorized password change attempts.

Fix this in Viewpower Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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