Physical memory disclosure via exposed PCIe slots
Published Nov 28, 2023 · Updated Feb 25, 2026
Information disclosure in BD FACSChorus 3.0 through 3.1 and 5.0 through 5.1 allows physically proximate attackers to read startup memory. The workstation chassis leaves internal PCIe slots physically accessible and permits an inserted DMA-capable card to capture RAM during startup. Physical access to the internal PCI bus is required; captured memory can expose a BitLocker encryption key without changing or interrupting the workstation.
Summary
What happened
Information disclosure in BD FACSChorus 3.0 through 3.1 and 5.0 through 5.1 allows physically proximate attackers to read startup memory. The workstation chassis leaves internal PCIe slots physically accessible and permits an inserted DMA-capable card to capture RAM during startup. Physical access to the internal PCI bus is required; captured memory can expose a BitLocker encryption key without changing or interrupting the workstation.
The record
- CVE
- CVE-2023-29063
- Published
- Nov 28, 2023
- Updated
- Feb 25, 2026
- Vendor
- Becton, Dickinson and Company
- Product
- FACSChorus
- Classifications
- CWE-1299, CWE-306, T1003
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 28, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record 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=3.0 <=3.1
- Affected versionversion=5.0 <=5.1
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