# CVE-2018-10601: Memory corruption in IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors

> An attacker on the same subnet can trigger a stack overflow via the echo service, potentially leading to code execution or denial of service.

- **Severity:** High 8.2 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9f6x-r29g-cv4j

## What is CVE-2018-10601?

CVE-2018-10601 is a high-severity memory corruption vulnerability in ICS-CERT IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors, published on 5 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IntelliVue Patient Monitors MP Series (including MP2/X2/MP30/MP50/MP70/NP90/MX700/800) Rev B-M, IntelliVue Patient Monitors MX (MX400-550) Rev J-M and (X3/MX100 for Rev M only), and Avalon Fetal/Maternal Monitors FM20/FM30/FM40/FM50 with software Revisions F.0, G.0 and J.3 have a vulnerability that exposes an "echo" service, in which an attacker-sent buffer to an attacker-chosen device address within the same subnet is copied to the stack with no boundary checks, hence resulting in stack overflow.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 18 products.


Products: Philips Avalon Fetal\/Maternal Monitors Fm20 Firmware, Philips Avalon Fetal\/Maternal Monitors Fm30 Firmware, Philips Avalon Fetal\/Maternal Monitors Fm40 Firmware, Philips Avalon Fetal\/Maternal Monitors Fm50 Firmware, Philips Intellivue Mp2 Firmware, Philips Intellivue Mp30 Firmware, Philips Intellivue Mp50 Firmware, Philips Intellivue Mp70 Firmware, Philips Intellivue Mx100 Firmware, Philips Intellivue Mx400 Firmware, Philips Intellivue Mx450 Firmware, Philips Intellivue Mx500 Firmware, Philips Intellivue Mx550 Firmware, Philips Intellivue Mx700 Firmware, Philips Intellivue Mx800 Firmware, Philips Intellivue Np90 Firmware, Philips Intellivue X2 Firmware, Philips Intellivue X3 Firmware.

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

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

## Is CVE-2018-10601 being exploited?

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

## Other vulnerabilities in ICS-CERT IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors

- [CVE-2018-10597](https://insights.sbomify.com/CVE-2018-10597/): Memory corruption in IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors (high 8.3)
- [CVE-2018-10599](https://insights.sbomify.com/CVE-2018-10599/): Information disclosure in IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10601 is a high-severity memory corruption vulnerability in ICS-CERT IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors, published on 5 Jun 2018. 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-2018-10601 in the wild and no public exploit code.

Affected product: ICS-CERT IntelliVue Patient Monitors, Avalon Fetal/Maternal Monitors. 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-10601/ (Markdown: https://insights.sbomify.com/CVE-2018-10601/index.md)
```

## Sources

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

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