Skip to content
Fencer Vulns
low 2.4

CVE-2023-29063 json

Lack of DMA Access Protections

published 2023-11-28 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-32666

cvss
2.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

The FACSChorus workstation does not prevent physical access to its PCI express (PCIe) slots, which could allow a threat actor to insert a PCI card designed for memory capture. A threat actor can then isolate sensitive information such as a BitLocker encryption key from a dump of the workstation RAM during startup.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-23-331-01 updated cvss 2.4

BD FACSChorus

  • Becton, Dickinson and Company (BD) BD FACSChorus (HP Z2 G5 workstation, shipped with FACSMelody Cell Sorter) 3.0, 3.1 Becton, Dickinson and Company (BD) BD FACSChorus (HP Z2 G9 workstation, shipped with FACSDiscover S8 Cell Sorter) 5.0, 5.1
    affected: mitigation “Ensure physical access controls are in place and only authorized end-users have access to the BD FACSChorus Software and respective workstation.” bd.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.4 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 2.4 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Becton, Dickinson and Company (BD) FACSChorus

Classification

Weakness
  • CWE-1299 Missing Protection Mechanism for Alternate Hardware Interface
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.