title: Unsecure Identity Verification
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.
problem types: CWE-287 Improper Authentication
affected:
{
defaultStatus: unaffected
platforms: [Windows, 64 bit]
product: FACSChorus
vendor: Becton, Dickinson and Company (BD)
versions:
lessThanOrEqual: 5.1, status: affected, version: 5.0, versionType: custom
lessThanOrEqual: 3.1, status: affected, version: 3.0, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: ADJACENT_NETWORK
availabilityImpact: NONE
baseScore: 3.8
baseSeverity: LOW
confidentialityImpact: LOW
integrityImpact: NONE
privilegesRequired: NONE
scope: CHANGED
userInteraction: REQUIRED
vectorString: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
version: 3.1
]
format: CVSS
scenarios: GENERAL
workarounds:
Vulnerabilities associated with the BD FACSChorus software and workstations will be addressed in an upcoming release. This bulletin will be updated when more information is available. Please check periodically for updates. Additionally, BD recommends the following mitigations and compensating controls to reduce risk associated with these vulnerabilities. The following recommendations apply to all vulnerabilities listed in this bulletin:
*  Ensure physical access controls are in place and only authorized end-users have access to the BD FACSChorus Software and respective workstation.
*  If the BD FACSChorus workstation is connected to the local network, ensure industry standard network security policies and procedures are followed.
*  Administrative access to the FACSChorus software and workstation should be strictly controlled by the customer in collaboration with their local IT security policy.