# CVE-2018-18589: MFSBGN03827 rev.1 - Microfocus Real User Monitoring 9.4.0 BPRDownload Java Deserialization Vulnerability

> Remote attackers can execute arbitrary code via Java deserialization in Micro Focus Real User Monitoring software.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2j4c-4vw2-9r77

## What is CVE-2018-18589?

CVE-2018-18589 is a medium-severity unsafe deserialization vulnerability in Microfocus Real User Monitoring, published on 23 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A potential Remote Arbitrary Code Execution vulnerability has been identified in Micro Focus' Real User Monitoring software, versions 9.26IP, 9.30, 9.40 and 9.50. The vulnerability could be exploited to execute arbitrary code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Microfocus Real User Monitoring.

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

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

## Is CVE-2018-18589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18589 is a medium-severity unsafe deserialization vulnerability in Microfocus Real User Monitoring, published on 23 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18589 in the wild and no public exploit code.

Affected product: Microfocus Real User Monitoring. 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-18589/ (Markdown: https://insights.sbomify.com/CVE-2018-18589/index.md)
```

## Sources

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

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