dbcve.org
Alaris Infusion CentralApplication · Bd

CVE-2022-47376

HIGH · 7.3 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to after 1.3.2 or later.
See remediation →
75/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Alaris Infusion Central software versions 1.1 through 1.3.2 contains a recoverable password vulnerability where credentials are stored in a reversible format after installation rather than being properly hashed or encrypted. This allows attackers who gain database or filesystem access to retrieve plaintext credentials.

MitigationOrganizations should update to a patched version of Alaris Infusion Central and immediately rotate any credentials that may have been exposed. Review installation documentation for vendor-provided password reset or migration tools.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Alaris Infusion CentralApplication
Affected:>= 1.1, <= 1.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of Alaris Infusion Central
    Locate the software installation directory or use system inventory tools to find the installed version number of Alaris Infusion Central. Check program files, installation logs, or the software itself for the version display.
    Affected if The installed version is >= 1.1 and <= 1.3.2, placing it within the affected range.
  2. Locate database files used by Alaris Infusion Central
    Search for database files associated with the application, typically in the installation directory or data folders. Common database formats include .mdb, .accdb, .db, or .sql files. Identify the primary data storage location.
    Affected if Database files exist and the application stores user credentials within them.
  3. Inspect stored credentials for encryption format
    Open or query the database files to examine how credentials are stored. Look for password fields and determine if the values appear as plaintext, encoded, or reversibly encrypted rather than being stored as salted hashes.
    Affected if Credentials in the database or config files are stored in plaintext, Base64-encoded, or using reversible encryption rather than being hashed with a one-way function.
  4. Check configuration files for credential storage settings
    Examine configuration files within the Alaris Infusion Central installation directory for settings related to credential storage, encryption keys, or password handling. Look for files with .config, .xml, .ini, or similar extensions.
    Affected if Configuration files contain encryption keys, credential storage parameters, or references to reversible encryption methods for passwords.
  5. Verify credential hashing implementation
    If you have access to the backend, inspect the authentication module or code that handles password storage to confirm whether a proper hashing algorithm (such as bcrypt, scrypt, or Argon2) is used versus a reversible method.
    Affected if The software uses reversible encryption or encoding for password storage instead of industry-standard one-way hashing.

A user is affected if Alaris Infusion Central version 1.1 through 1.3.2 is installed and credentials are stored in a reversible format in database or configuration files rather than being properly hashed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.3.2
Interim mitigation

Organizations should update to a patched version of Alaris Infusion Central and immediately rotate any credentials that may have been exposed. Review installation documentation for vendor-provided password reset or migration tools.

Fix this in Alaris Infusion Central Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47376 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data