Cyber Resilience

CVE-2023-51582

Voltronicpower Viewpower 1.04.21353

Published
03 May 2024
Modified
09 July 2025
CVSS Score v3 9.8
Click a component to see what it means
Raw vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 72th percentile
Risk Priority 77 floored blend · peak EPSS

Summary

CVE-2023-51582 is a critical-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Voltronicpower Viewpower. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 28% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Voltronic Power ViewPower LinuxMonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Voltronic Power ViewPower. Authentication is not required to exploit this vulnerability. The specific flaw exists within…

more

the LinuxMonitorConsole class. The issue results from an exposed dangerous method. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-22035.

CWE(s)
CWE-749

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-51575Same product: Voltronicpower Viewpower
CVE-2023-51584Same product: Voltronicpower Viewpower
CVE-2023-51581Same product: Voltronicpower Viewpower
CVE-2023-51583Same product: Voltronicpower Viewpower
CVE-2023-51573Same product: Voltronicpower Viewpower
CVE-2023-51578Same product: Voltronicpower Viewpower
CVE-2023-51574Same product: Voltronicpower Viewpower
CVE-2023-51577Same product: Voltronicpower Viewpower
CVE-2023-51593Same product: Voltronicpower Viewpower
CVE-2023-51586Same product: Voltronicpower Viewpower

Affected Assets

voltronicpower
viewpower
1.04.21353

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V8.2.1

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Access enforcement directly stops unauthorized callers from invoking dangerous API methods or functions.

AC-6 Least Privilege good match

Least privilege restricts which users or processes may reach dangerous methods, limiting exposure.

CM-7 Least Functionality good match

Least functionality removes or disables non-essential dangerous methods from the exposed interface altogether.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.

PR.PS-06 mostly match
prevents

Secure SDLC practices stop developers from exposing dangerous functions in the first place.

ID.RA-01 partial match
prevents

Vulnerability identification processes will surface exposed dangerous methods during assessment.

PR.IR-01 partial match
prevents

Logical access controls at the network/environment layer can limit reachability of exposed functions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.

A.8.18 Use of privileged utility programs partial match
degrades

Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.

A.8.2 Privileged access rights partial match
prevents

Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle requires removal or protection of dangerous APIs during design and coding.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate that dangerous methods are not exposed in interfaces.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Ubuntu 22.04 (3 rules)
  • V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
  • V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
  • V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
  • V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749

References