# CVE-2022-47376: Hardcoded credentials in Alaris Infusion Central

> Recoverable passwords in Alaris Infusion Central allow attackers to bypass authentication and potentially access stored personal data.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-h3m9-vw67-pc8x

## What is CVE-2022-47376?

CVE-2022-47376 is a high-severity vulnerability in Alaris Infusion Central, published on 13 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Alaris Infusion Central software, versions 1.1 to 1.3.2, may contain a recoverable password after the installation. No patient health data is stored in the database, although some site installations may choose to store personal data.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-257 (Storing Passwords in a Recoverable Format)

## Which versions are affected by CVE-2022-47376?

It affects 1 product.


Products: Bd Alaris Infusion Central.

## How do I fix CVE-2022-47376?

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

## Is CVE-2022-47376 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47376 and fix it if it is affected.

What it is: CVE-2022-47376 is a high-severity vulnerability in Alaris Infusion Central, published on 13 Jun 2023. 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-2022-47376 in the wild and no public exploit code.

Affected product: Alaris Infusion Central. 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-2022-47376/ (Markdown: https://insights.sbomify.com/CVE-2022-47376/index.md)
```

## Sources

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

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