dbcve.org
Alaris 8015 Pcu FirmwareOperating system · Bd

CVE-2023-30560

MEDIUM · 6.8 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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 configuration from the PCU can be modified without authentication using physical connection to the PCU.

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

This vulnerability allows unauthorized modification of PCU (Power Control Unit) configuration without authentication when an attacker has physical access to the device. The lack of authentication on the configuration interface enables a physically proximate attacker to alter device settings.

MitigationImplement authentication mechanisms for all configuration changes on the PCU, combined with physical security controls restricting access to the device.

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 8015 Pcu FirmwareOperating system
Affected:<= 12.1.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 device model
    Locate the physical device or system documentation to confirm it is a BD Alaris 8015 PCU (Power Control Unit)
    Affected if The device is a BD Alaris 8015 PCU model
  2. Check the firmware version
    Access the device's system information or firmware version display (typically via the device's built-in interface, console, or management software) and note the firmware version number
    Affected if The installed firmware version is 12.1.3 or any version lower (e.g., 12.1.2, 12.0.x, etc.)
  3. Determine if the configuration interface is physically accessible
    Inspect the physical device to determine whether the configuration port/interface (such as the front panel or service port) is exposed and accessible without barriers
    Affected if The configuration interface can be physically accessed by a person with proximity to the device
  4. Verify if authentication is required for configuration changes
    Attempt to access the PCU configuration settings (or review device security settings) to determine whether the system prompts for any authentication (password, PIN, credentials) before allowing configuration modifications
    Affected if No authentication is required to modify PCU configuration settings, or the configuration interface accepts changes without prompting for credentials

You are affected if you have a BD Alaris 8015 PCU running firmware version 12.1.3 or lower and the configuration interface can be accessed physically without requiring authentication.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.1.3
Interim mitigation

Implement authentication mechanisms for all configuration changes on the PCU, combined with physical security controls restricting access to the device.

Recommended fix Moderate confidence

Alaris 8015 PCU Firmware version 12.1.4 or later (contact BD for exact fixed version)

  1. Contact BD (Becton, Dickinson) customer support to obtain the updated firmware version for the Alaris 8015 PCU
  2. Request firmware version 12.1.4 or later (or the latest available version) which contains the authentication fix
  3. Follow BD's official firmware update procedure for the Alaris 8015 PCU, ensuring the update is performed in accordance with their documented process
  4. After upgrading, verify that the configuration now requires proper authentication before modification
  5. Document the firmware version upgrade in your change management system
Caveat Review BD release notes for any operational changes or configuration differences in the updated firmware

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Alaris 8015 Pcu Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30560 — 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-2023-30560 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