Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated remote attacker use the product’s web interface to take over UPS management functions. Impact can include changing the admin password, altering configuration, discovering attached UPS devices, shutting devices down, and configuring commands tied to UPS shutdown events.
Executive priority
Treat as urgent for environments where UPS management can affect business continuity or physical operations. Prioritize internet-exposed or broadly reachable instances first, then internal systems supporting critical services.
Technical view
CVE-2022-43110 affects Voltronic Power ViewPower through 1.04-21353 and PowerShield Netguard before 1.04-23292. It is an unauthenticated remote configuration issue in an unspecified web interface, mapped to missing authorization/authentication and direct request weaknesses, with CVSS 3.1 score 9.8.
Likely exposure
Highest exposure is any affected ViewPower or PowerShield Netguard web interface reachable from untrusted networks. Business risk is concentrated where these tools manage UPS devices supporting servers, facilities, security systems, or industrial operations.
Exploitation context
The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is still severe because the attack is network-reachable, requires no credentials or user interaction, and can affect power-control operations.
Researcher notes
Evidence identifies powerful unauthenticated configuration capability but does not specify the exact endpoint or request behavior. Avoid assuming exploit mechanics beyond the described web-interface access. The affected CPE data in the bundle is incomplete despite product/version details in the description.
Mitigation direction
- Identify all ViewPower and PowerShield Netguard deployments and versions.
- Upgrade PowerShield Netguard to 1.04-23292 or later where vendor guidance supports it.
- Check vendor and CISA guidance for current ViewPower remediation status.
- Restrict web interface access to trusted management networks only.
- Place UPS management systems behind firewalls or VPN-controlled administrative access.
- Rotate web admin credentials after remediation if exposure is suspected.
Validation and detection
- Inventory exposed web interfaces for affected product names and versions.
- Confirm the interface is not reachable from the public internet.
- Review configuration and admin password changes for unauthorized activity.
- Check UPS shutdown settings and configured OS command actions.
- Verify firewall, VPN, and segmentation controls around UPS management hosts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-425: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-43110 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ready2disclose.com/vpow-31491-43110/CVE reference
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-182-05CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Direct Request ('Forced Browsing')
Direct Request ('Forced Browsing') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.