CVE Intelligence
Skip to main content
CRITICAL

CVE-2024-48971

CVE-2024-48971 — Clinician Password and Serial Number Clinician Password are hard-coded in Life2000 Ventilator

The Clinician Password and Serial Number Clinician Password are hard-coded into the ventilator in plaintext form. This could allow an attacker to obtain the password off the ventilator and use it to gain unauthorized access to the device, with clinician privileges.

Published Updated Sources: cvelistV5, Baxter

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

baxter

2 products listed

CVSS base

9.3

CRITICAL

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

baxter

Products (2)

life2000 ventilation systemlife2000 ventilator firmware

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9.3CVSS 3.1CRITICAL——cvelistV5

Weakness & attack patterns

  • CWE-798

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1552.001Unsecured Credentials: Credentials in files
  • T1078.001Valid Accounts: Default Accounts

References

1 on the record

Elsewhere on this site

  • baxterevery CVE for this vendor
  • CWE-798other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.