# CVE-2017-9657: Business logic in IntelliVue MX40 Patient Worn Monitor

> Attackers can cause a patient monitor to fail local alarming during network re-association, delaying treatment for critical events.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 30 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-32rc-pv7x-94gg

## What is CVE-2017-9657?

CVE-2017-9657 is a medium-severity vulnerability in Philips IntelliVue MX40 Patient Worn Monitor, published on 30 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Under specific 802.11 network conditions, a partial re-association of the Philips IntelliVue MX40 Version B.06.18 WLAN monitor to the central monitoring station is possible. In this state, the central monitoring station can indicate the MX40 is not connected or associated to the central monitor, and thus should be operating in local monitoring mode (local audio-on, screen-on), but the MX40 WLAN itself can instead still be operating in telemetry mode (local audio-off, screen-off). If a patient experiences an alarm event and clinical staff expects the MX40 to provide local alarming when it is not available from the local device, a delay of treatment can occur. CVSS v3 base score: 6.5, CVSS vector string: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Philips has released software update, Version B.06.18, to fix the improper cleanup on thrown exception vulnerability, and implement mitigations to reduce the risk associated with the improper handling of exceptional conditions vulnerability. The software update implements messaging and alarming on the MX40 and at the central monitoring station, when the MX40 disconnects from the access point.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-460 (Improper Cleanup on Thrown Exception)

## Which versions are affected by CVE-2017-9657?

It affects 1 product.


Products: Philips Intellivue Mx40 Firmware.

## How do I fix CVE-2017-9657?

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

## Is CVE-2017-9657 being exploited?

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

## Other vulnerabilities in Philips IntelliVue MX40 Patient Worn Monitor

- [CVE-2017-9658](https://insights.sbomify.com/CVE-2017-9658/): Denial of service in IntelliVue MX40 Patient Worn Monitor (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9657 and fix it if it is affected.

What it is: CVE-2017-9657 is a medium-severity vulnerability in Philips IntelliVue MX40 Patient Worn Monitor, published on 30 Apr 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-2017-9657 in the wild and no public exploit code.

Affected product: Philips IntelliVue MX40 Patient Worn Monitor. 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-2017-9657/ (Markdown: https://insights.sbomify.com/CVE-2017-9657/index.md)
```

## Sources

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

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