Skip to content
Fencer Vulns
low 3.8

CVE-2023-29062 json

Unsecure Identity Verification

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

cvss
3.8
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 22%
public exploits
0
none known

Summary

The Operating System hosting the FACSChorus application is configured to allow transmission of hashed user credentials upon user action without adequately validating the identity of the requested resource. This is possible through the use of LLMNR, MBT-NS, or MDNS and will result in NTLMv2 hashes being sent to a malicious entity position on the local network. These hashes can subsequently be attacked through brute force and cracked if a weak password is used. This attack would only apply to domain joined systems.

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 3.8

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

Exploit prediction

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

CVSS scores

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

Affected products

  • Becton, Dickinson and Company (BD) FACSChorus

Classification

Weakness

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.