CVE-2023-29061VulnerabilityPublished 28 Nov 2023Updated 3 Jun 2025

CVE-2023-29061: Becton, Dickinson and Company (BD) FACSChorus · Missing Authentication

Affects Becton, Dickinson and Company (BD) FACSChorusSource CVE Database V5

Not known to be exploited · CVSS 5.2 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Becton, Dickinson and Company (BD) FACSChorus	Affected =5.0 =3.0	Fixed in–

AI-suggested

To mitigate CVE-2023-29061 effectively, European organizations should implement the following specific measures: 1) Immediately enforce physical security controls around FACSChorus workstations, including restricted access to laboratory areas and surveillance to prevent unauthorized physical access. 2) Where possible, configure BIOS passwords manually on all affected devices to prevent unauthorized BIOS access; if the vendor does not provide a patch, organizations should engage with BD support for guidance or firmware updates. 3) Implement hardware-based security features such as Trusted Platform Module (TPM) and secure boot to limit unauthorized boot modifications. 4) Maintain strict inventory and asset management to quickly identify affected devices and monitor their physical security status. 5) Conduct regular audits of BIOS settings and system configurations to detect unauthorized changes promptly. 6) Train laboratory personnel on the risks of physical access vulnerabilities and enforce policies to prevent unauthorized device handling. 7) Develop incident response plans that include procedures for BIOS compromise scenarios to minimize downtime and data integrity risks. 8) Collaborate with BD and industry groups to stay informed about patches or firmware updates addressing this vulnerability.

Description

There is no BIOS password on the FACSChorus workstation. A threat actor with physical access to the workstation can potentially exploit this vulnerability to access the BIOS configuration and modify the drive boot order and BIOS pre-boot authentication.

Impact

For European organizations, particularly those in healthcare, biomedical research, and clinical diagnostics, this vulnerability poses a tangible risk. FACSChorus workstations are integral to flow cytometry workflows, and any compromise could disrupt diagnostic processes or research outcomes. An attacker modifying BIOS settings could introduce persistent malware or alter system behavior, potentially leading to inaccurate test results or data loss. This could undermine patient safety, research validity, and regulatory compliance with frameworks such as GDPR and medical device regulations. Additionally, the physical access requirement means that insider threats or unauthorized visitors in laboratories could exploit this vulnerability. The impact on availability is significant, as BIOS misconfiguration can render devices unbootable or unstable, causing downtime in critical laboratory operations. Although confidentiality impact is rated as none, the integrity and availability impacts are sufficient to cause operational and reputational damage. European healthcare institutions, which often have stringent security and privacy requirements, must consider this vulnerability seriously to maintain trust and compliance.

CWE-306Missing Authentication for Critical Function (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

bd.com/en-us/about-bd/cybersecurity/bulletin/bd-facschorus-software (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 21:55 UTC

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats