Default credentials are used in the above listed BD Diagnostic Solutions products. If exploited, threat actors may be able to access, modify or delete data, including sensitive information such as protected health information (PHI) and personally identifiable information (PII). E...
Vendor
Becton Dickinson & Co vulnerabilities
8 published CVES affecting Becton Dickinson & Co, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 0
- High
- 2
- Medium
- 5
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Products
- BD Alarisâ„¢ Point-of-Care Unit (PCU) Model 8015 2
- BD Alarisâ„¢ Systems Manager 2
- BD Alarisâ„¢ Guardrailsâ„¢ Editor 1
- BD Alaris™ Point-of-Care Unit (PCU) Model 8015 1
- BD BACTEC™ Blood Culture System 1
- BD COR™ System 1
- BD EpiCenter™ Microbiology Data Management System 1
- BD MAX™ System 1
- BD Phoenix™ M50 Automated Microbiology System 1
- BD Synapsys™ Informatics Solution 1
- CQI Reporter 1
Latest Becton Dickinson & Co CVEs
Newest publication first
-
HighCVSS 8.0 EPSS 0.24%
-
CVE-2023-30565 CQI Data Sniffing
PublishedLowCVSS 3.5 EPSS 0.14%An insecure connection between Systems Manager and CQI Reporter application could expose infusion data to an attacker.
-
MediumCVSS 6.9 EPSS 0.29%
Alaris Systems Manager does not perform input validation during the Device Import Function.
-
HighCVSS 8.2 EPSS 0.44%
A malicious file could be uploaded into a System Manager User Import Function resulting in a hijacked session.
-
MediumCVSS 6.7 EPSS 0.18%
A GRE dataset file within Systems Manager can be tampered with and distributed to PCUs.
-
MediumCVSS 6.1 EPSS 0.19%
The data flowing between the PCU and its modules is insecure. A threat actor with physical access could potentially read or modify data by attaching a specially crafted device while an infusion is running.
-
MediumCVSS 6.8 EPSS 0.30%
The configuration from the PCU can be modified without authentication using physical connection to the PCU.
-
MediumCVSS 5.7 EPSS 0.18%
The firmware update package for the wireless card is not properly signed and can be modified.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.