# CVE-2023-43029: IBM Storage Virtualize vSphere Remote Plug-in information disclosure

> A remote user can obtain sensitive credential information from the IBM Storage Virtualize vSphere Remote Plug-in after deployment.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2025
- **Updated:** 17 Aug 2025
- **Also known as:** GHSA-q334-476c-x4rf

## What is CVE-2023-43029?

CVE-2023-43029 is a medium-severity vulnerability in IBM Storage Virtualize vSphere Remote Plug-in, published on 21 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Storage Virtualize vSphere Remote Plug-in 1.0 and 1.1 could allow a remote user to obtain sensitive credential information after deployment.

Weakness: CWE-526 (Cleartext Storage of Sensitive Information in an Environment Variable)

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

It affects 1 product.


Products: Ibm Storage Virtualize Plugin for Vsphere.

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

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

## Is CVE-2023-43029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43029 is a medium-severity vulnerability in IBM Storage Virtualize vSphere Remote Plug-in, published on 21 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-43029 in the wild and no public exploit code.

Affected product: IBM Storage Virtualize vSphere Remote Plug-in. 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-43029/ (Markdown: https://insights.sbomify.com/CVE-2023-43029/index.md)
```

## Sources

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

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