CVE-2023-29065 json
Overly Permissive Access Policy
published 2023-11-28 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-32668
- cvss
- 4.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
The FACSChorus software database can be accessed directly with the privileges of the currently logged-in user. A threat actor with physical access could potentially gain credentials, which could be used to alter or destroy data stored in the database.
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 4.1
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.1affected: 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
- partial
- Assessed
- 2 y ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.1 | CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected products
- Becton, Dickinson and Company (BD) FACSChorus
Classification
References
Sources
- CVE List CVE-2023-29065
- NVD CVE-2023-29065
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.