Alaris Systems ManagerApplication · Bd

CVE-2023-30563

HIGH · 8.2 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to after 12.3 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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
A malicious file could be uploaded into a System Manager User Import Function resulting in a hijacked session.

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 vulnerability allows authenticated users to upload malicious files through a System Manager User Import function, which can lead to session hijacking. This appears to stem from improper input validation and insufficient sanitization of uploaded files in the import mechanism.

MitigationImplement strict allowlist-based file type validation, sanitize uploaded content before processing, and enforce secure session management with proper token handling to prevent session hijacking.

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 Systems ManagerApplication
Affected:<= 12.3

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

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

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 the installed product
    Locate the Bd Alaris Systems Manager application in your environment and confirm the software name matches 'Bd Alaris Systems Manager' or 'Alaris Systems Manager'
    Affected if The product is not Bd Alaris Systems Manager
  2. Check the installed version
    Access the System Manager admin interface or check system information to determine the exact version number of the software
    Affected if The installed version is 12.3 or any version lower than 12.3 (e.g., 12.2, 12.1, 12.0)
  3. Verify User Import feature is accessible
    Check if the System Manager User Import function is enabled and accessible within the administrative interface under the user management or administration section
    Affected if The User Import feature is enabled and accessible to authenticated users
  4. Confirm authenticated user access
    Determine whether standard authenticated users (non-admin) have permissions to access and use the User Import functionality
    Affected if Authenticated users have privileges to access the User Import function

You are affected if Bd Alaris Systems Manager version 12.3 or lower is installed AND the User Import feature is accessible to authenticated users in your environment.

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 12.3
Interim mitigation

Implement strict allowlist-based file type validation, sanitize uploaded content before processing, and enforce secure session management with proper token handling to prevent session hijacking.

Fix this in Alaris Systems Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-30563 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