Physical firmware modification via invalid wireless-card signature
Published Jul 13, 2023 · Updated Aug 2, 2024
Improper signature validation in BD Alaris PCU Model 8015 firmware versions 12.1.3 and earlier allows attackers to modify wireless card updates. The wireless-card firmware update package accepts content that is not properly signed, allowing a modified package to be installed. Physical access to the PCU is required; exploitation can disrupt device availability and expose limited information, while BD reports no observed exploitation.
Summary
What happened
Improper signature validation in BD Alaris PCU Model 8015 firmware versions 12.1.3 and earlier allows attackers to modify wireless card updates. The wireless-card firmware update package accepts content that is not properly signed, allowing a modified package to be installed. Physical access to the PCU is required; exploitation can disrupt device availability and expose limited information, while BD reports no observed exploitation.
The record
- CVE
- CVE-2023-30559
- Published
- Jul 13, 2023
- Updated
- Aug 2, 2024
- Vendor
- Becton, Dickinson and Company
- Product
- BD Alaris Point-of-Care Unit (PCU) Model 8015
- Classifications
- CWE-345, CWE-20, CWE-287, T1601
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=12.1.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo