CVE-2023-51572
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 Pro getMacAddressByIp Command Injection 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 getMacAddressByIP function. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-21163.
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 confidenceCommand injection vulnerability in the getMacAddressByIP function of Voltronic Power ViewPower Pro. The application fails to validate user-supplied input before passing it to a system call, allowing unauthenticated remote attackers to execute arbitrary code with SYSTEM privileges.
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= 2.0-22165CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ViewPower Pro installationLook for ViewPower Pro installation directories or check for processes named ViewPower, ViewPowerPro, or associated services. Common paths may include C:\Program Files\ViewPower Pro or similar. Check running services for Voltronic or ViewPower entries.Affected if ViewPower Pro is installed on the system
-
Identify installed versionLocate version information in installation directories, check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\VoltronicPower or similar, or look for version.txt, about, or help files within the application directory.Affected if Version is 2.0-22165 or earlier (vulnerable release)
-
Verify getMacAddressByIP function accessibilityThis vulnerability exists in the web interface component. Check if the ViewPower Pro web service (typically on ports 80/443 or custom ports like 8080) is running and accessible. The getMacAddressByIP function is a network-related API endpoint.Affected if The web interface is exposed and the application runs a vulnerable version
-
Assess network exposureDetermine if the ViewPower Pro web service is accessible from unauthenticated network positions. Check firewall rules, binding addresses (listen on 0.0.0.0 vs 127.0.0.1), and whether the service is exposed to internal or external networks.Affected if The vulnerable web interface is accessible from network segments where untrusted users can send requests
You are affected if ViewPower Pro version 2.0-22165 or earlier is installed AND the web interface with the getMacAddressByIP function is network-accessible to unauthenticated users.
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 dataRestrict network access to the ViewPower Pro service and apply vendor patches when available. Until a patch is released, consider network segmentation to isolate the affected system.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51572 — 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-51572 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