# CVE-2024-48973: Debug port on Life2000 Ventilator serial interface is enabled by default

> Attackers can access unencrypted debug ports on Life2000 ventilators to disclose information or alter device settings due to default configurations.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/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:** 14 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-xx59-963p-2v9w

## What is CVE-2024-48973?

CVE-2024-48973 is a critical vulnerability in Baxter Life2000 Ventilation System, published on 14 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The debug port on the ventilator's serial interface is enabled by default. This could allow an attacker to send and receive messages over the debug port (which are unencrypted; see 3.2.1) that result in unauthorized disclosure of information and/or have unintended impacts on device settings and performance.

Weakness: CWE-1263 (Improper Physical Access Control)

## Which versions are affected by CVE-2024-48973?


## How do I fix CVE-2024-48973?

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

## Is CVE-2024-48973 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48973 and fix it if it is affected.

What it is: CVE-2024-48973 is a critical vulnerability in Baxter Life2000 Ventilation System, published on 14 Nov 2024. 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-2024-48973 in the wild and no public exploit code.

Affected product: Baxter Life2000 Ventilation System. 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-2024-48973/ (Markdown: https://insights.sbomify.com/CVE-2024-48973/index.md)
```

## Sources

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

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