dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51579

HIGH · 7.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 →
80/100
Remediation priority · High
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 Incorrect Permission Assignment Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Voltronic Power ViewPower. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the product installer. The issue results from incorrect permissions set on folders. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-22025.

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

The vulnerability exists in the ViewPower installer which sets overly permissive file system permissions on certain folders. This allows a low-privileged local attacker to modify or replace executables that run with elevated (SYSTEM) privileges, achieving privilege escalation.

MitigationReview and correct folder permissions set by the ViewPower installer, ensuring non-admin users cannot write to directories containing executables that run with elevated privileges. Use tools like icacls to restrict permissions appropriately.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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. Check if ViewPower is installed
    Look for ViewPower installation directories. Common locations include C:\Program Files\ViewPower, C:\Program Files (x86)\ViewPower, or the installation directory specified during setup. Check for the presence of ViewPower executables and the software in Add/Remove Programs.
    Affected if ViewPower is installed on the system
  2. Verify installed version
    Check the version of installed ViewPower software. Right-click the ViewPower executable (typically named ViewPower.exe or similar), select Properties, and check the File Version or Product Version field. You can also check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for ViewPower entries.
    Affected if Installed version equals 1.04.21353
  3. Identify ViewPower installation folders
    Locate all directories where ViewPower is installed. Check Program Files and Program Files (x86) directories, as well as any custom installation paths. Note all folders containing executable files related to ViewPower.
    Affected if ViewPower is installed in any directory on the system
  4. Inspect folder permissions on ViewPower directories
    Right-click each ViewPower installation folder containing executables, select Properties, go to the Security tab, and examine the permissions for Users and other non-admin groups. Use the command 'icacls "<folder_path>"' to list all permissions in detail.
    Affected if Non-admin users (such as Users group) have Write or Modify permissions on folders containing ViewPower executables
  5. Check for service executables running with elevated privileges
    Open Services (services.msc), look for services related to ViewPower, and note their executable paths. Check if these executables reside in folders with overly permissive permissions. Use 'sc query' or check service properties to identify ViewPower services.
    Affected if ViewPower services run with SYSTEM privileges and their executable files are in folders writable by low-privileged users

The system is affected if ViewPower version 1.04.21353 is installed and non-admin users have Write or Modify permissions on directories containing executables that run as SYSTEM services.

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

Review and correct folder permissions set by the ViewPower installer, ensuring non-admin users cannot write to directories containing executables that run with elevated privileges. Use tools like icacls to restrict permissions appropriately.

Fix this in Viewpower Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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