# CVE-2023-51587: Voltronic Power ViewPower getModbusPassword Missing Authentication Information Disclosure Vulnerability

> Remote attackers can access the getModbusPassword method without authentication to disclose stored credentials, leading to potential further compromise.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g29m-vq8m-35pg

## What is CVE-2023-51587?

CVE-2023-51587 is a high-severity missing authorization vulnerability in Voltronic Power ViewPower, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Voltronic Power ViewPower getModbusPassword Missing Authentication Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Voltronic Power ViewPower. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the getModbusPassword method. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-22073.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-51587?

It affects 1 product.


Products: Voltronicpower Viewpower.

## How do I fix CVE-2023-51587?

No fix has been published for CVE-2023-51587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-51587 being exploited?

There is no known exploitation of CVE-2023-51587 in the wild and no public exploit code.

## Other vulnerabilities in Voltronic Power ViewPower

- [CVE-2023-51574](https://insights.sbomify.com/CVE-2023-51574/): Voltronic Power ViewPower updateManagerPassword Exposed Dangerous Method Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2023-51575](https://insights.sbomify.com/CVE-2023-51575/): Voltronic Power ViewPower MonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-51576](https://insights.sbomify.com/CVE-2023-51576/): Voltronic Power ViewPower Deserialization of Untrusted Data Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-51581](https://insights.sbomify.com/CVE-2023-51581/): Voltronic Power ViewPower MacMonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-51582](https://insights.sbomify.com/CVE-2023-51582/): Voltronic Power ViewPower LinuxMonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51587 and fix it if it is affected.

What it is: CVE-2023-51587 is a high-severity missing authorization vulnerability in Voltronic Power ViewPower, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51587 in the wild and no public exploit code.

Affected product: Voltronic Power ViewPower. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-51587/ (Markdown: https://insights.sbomify.com/CVE-2023-51587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-51587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-51587
- OSV: https://osv.dev/vulnerability/CVE-2023-51587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-51587/
Summaries are generated and may contain mistakes; the official description above is the record.