# CVE-2019-4118: Information disclosure in Multicloud Manager

> A local attacker with admin privileges can obtain highly sensitive information during deployment in IBM Multicloud Manager.

- **Severity:** Medium 4.4 (`CVSS:3.0/A:N/UI:N/AC:L/C:H/AV:L/I:N/PR:H/S:U/RL:O/RC:C/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-976h-wp46-vfh8

## What is CVE-2019-4118?

CVE-2019-4118 is a medium-severity vulnerability in IBM Multicloud Manager, published on 11 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Multicloud Manager 3.1.0, 3.1.1, and 3.1.2 ibm-mcm-chart could allow a local attacker with admin privileges to obtain highly sensitive information upon deployment. IBM X-Force ID: 158144.

## Which versions are affected by CVE-2019-4118?

It affects 1 product.


Products: Ibm Multicloud Manager.

## How do I fix CVE-2019-4118?

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

## Is CVE-2019-4118 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4118 and fix it if it is affected.

What it is: CVE-2019-4118 is a medium-severity vulnerability in IBM Multicloud Manager, published on 11 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4118 in the wild and no public exploit code.

Affected product: IBM Multicloud Manager. 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-2019-4118/ (Markdown: https://insights.sbomify.com/CVE-2019-4118/index.md)
```

## Sources

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

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