# CVE-2018-6487: MFSBGN03799 rev.1 - Micro Focus UCMDB, Remote Disclosure of Information

> Remote attackers can exploit Micro Focus UCMDB to disclose sensitive information, requiring immediate patching by administrators.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-48r9-726w-jrh5

## What is CVE-2018-6487?

CVE-2018-6487 is a critical vulnerability in Micro Focus Universal CMDB Foundation Software, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Remote Disclosure of Information in Micro Focus Universal CMDB Foundation Software, version numbers 10.10, 10.11, 10.20, 10.21, 10.22, 10.30, 10.31, 4.10, 4.11. This vulnerability could be remotely exploited to allow disclosure of information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-6487?

It affects 1 product.


Products: Microfocus Universal Cmdb Foundation Software.

## How do I fix CVE-2018-6487?

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

## Is CVE-2018-6487 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6487 and fix it if it is affected.

What it is: CVE-2018-6487 is a critical vulnerability in Micro Focus Universal CMDB Foundation Software, published on 20 Feb 2018. 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-2018-6487 in the wild and no public exploit code.

Affected product: Micro Focus Universal CMDB Foundation Software. 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-2018-6487/ (Markdown: https://insights.sbomify.com/CVE-2018-6487/index.md)
```

## Sources

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

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