BD FACSChorus up to 3.1/5.1 PCI Express Slot missing protection mechanism for alternate hardware interface
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in BD FACSChorus up to 3.1/5.1. This affects an unknown part of the component PCI Express Slot Handler. This manipulation causes missing protection mechanism for alternate hardware interface. This vulnerability is registered as CVE-2023-29063. It is feasible to perform the attack on the physical device. No exploit is available.
Details
A vulnerability has been found in BD FACSChorus up to 3.1/5.1 and classified as problematic. Affected by this vulnerability is some unknown functionality of the component PCI Express Slot Handler. The manipulation with an unknown input leads to a missing protection mechanism for alternate hardware interface vulnerability. The CWE definition for the vulnerability is CWE-1299. The lack of protections on alternate paths to access
control-protected assets (such as unprotected shadow registers
and other external facing unguarded interfaces) allows an
attacker to bypass existing protections to the asset that are
only performed against the primary path. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was published 11/29/2023. The advisory is shared at bd.com. This vulnerability is known as CVE-2023-29063 since 03/30/2023. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.4
VulDB Base Score: 2.4
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 2.4
CNA Vector (Becton, Dickinson and Company (BD)): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Missing protection mechanism for alternate hardware interfaceCWE: CWE-1299
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/30/2023 🔍11/29/2023 🔍
11/29/2023 🔍
11/29/2023 🔍
Sources
Advisory: bd.comStatus: Confirmed
CVE: CVE-2023-29063 (🔍)
GCVE (CVE): GCVE-0-2023-29063
GCVE (VulDB): GCVE-100-246325
Entry
Created: 11/29/2023 06:47Changes: 11/29/2023 06:47 (47)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.