dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2022-43110

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-22
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 through 1.04-21353 and PowerShield Netguard before 1.04-23292 allows a remote attacker to configure the system via an unspecified web interface. An unauthenticated remote attacker can make changes to the system including: changing the web interface admin password, view/change system configuration, enumerate connected UPS devices and shut down connected UPS devices. This extends to being able to configure operating system commands that should run if the system detects a connected UPS shutting down.

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

An unauthenticated remote attacker can access an unspecified web interface in Voltronic Power ViewPower (through 1.04-21353) and PowerShield Netguard (before 1.04-23292) to change admin passwords, view/modify system configuration, enumerate and shut down connected UPS devices, and configure OS commands that execute on UPS shutdown events.

MitigationRestrict network access to the UPS management web interface to trusted networks only, and apply vendor patches when available. Consider network segmentation to isolate UPS management interfaces from untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.1/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. Locate the web management interface
    Identify whether Voltronic Power ViewPower or PowerShield Netguard web interface is running on your network. Check for HTTP/HTTPS services on common ports (typically 80, 443, 8080, 8443) or review your network inventory for these applications.
    Affected if The web interface is exposed on the network without network segmentation or VPN access controls.
  2. Determine the installed software version
    Access the web interface login page and look for version information, typically displayed in the footer, About page, or system information section. Alternatively, check the application binaries or configuration files on the server for version metadata.
    Affected if The installed version cannot be determined or is older than the current stable release.
  3. Test for authentication bypass
    Attempt to access administrative URLs or API endpoints directly without providing credentials. Common paths to test include /admin, /config, /settings, or API endpoints that should require authentication. Observe if administrative functionality is accessible without a login session.
    Affected if Administrative pages, configuration options, or sensitive API calls return successful responses without authentication credentials.
  4. Verify credential change capability
    After confirming unauthenticated access is possible, test whether the admin password can be modified or new admin accounts can be created without prior authentication.
    Affected if You can modify administrator credentials or create new admin users without being logged in.
  5. Inspect UPS management capabilities
    If unauthenticated access is confirmed, check whether connected UPS devices can be enumerated, their status viewed, or shutdown commands issued through the interface.
    Affected if UPS device enumeration, status viewing, or shutdown commands execute successfully without authentication.

Your environment is affected if the ViewPower or PowerShield Netguard web interface is network-accessible and either allows unauthenticated administrative access or is running a version that predates the current release.

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 the UPS management web interface to trusted networks only, and apply vendor patches when available. Consider network segmentation to isolate UPS management interfaces from untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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