CVE-2023-29060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe FACSChorus workstation operating system does not restrict what devices can interact with its USB ports. If exploited, a threat actor with physical access to the workstation could gain access to system information and potentially exfiltrate data.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe FACSChorus workstation operating system lacks USB device restriction controls, allowing any USB device to be connected to the system. A threat actor with physical access could connect malicious USB devices (storage, HID emulators, or keyloggers) to access system information or exfiltrate data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.0= 5.1= 3.0= 3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FACSChorus versionOpen the FACSChorus application and navigate to Help > About, or check the Windows Programs and Features list for 'BD FACSChorus' to confirm the installed version numberAffected if The installed version is 3.0, 3.1, 5.0, or 5.1 - only these exact versions are affected
-
Verify Windows USB restriction policyOpen Local Group Policy Editor (gpedit.msc) and navigate to Computer Configuration > Administrative Templates > System > Device Installation. Check if 'Prevent installation of removable devices' is enabled, or check the equivalent registry key at HKLM\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall\Restrictions\DenyDeviceClassesAffected if The policy is not configured or is disabled, meaning USB device restrictions are not enforced
-
Check USB device drivers statusOpen Device Manager and expand the 'Universal Serial Bus controllers' section. Look for USB mass storage device drivers or any USB devices that are currently connected or have been connected. Alternatively, run 'pnputil /enum-drivers' to list all installed USB driver packagesAffected if USB mass storage drivers are present and no restrictive policies are in place to block them
-
Inspect physical USB port controlsPhysically inspect all USB ports on the workstation for the presence of USB port blockers, locks, or physical obstruction devices. Also check if the system has software-based USB disablement via BIOS/UEFI settingsAffected if No physical port blockers are present AND no BIOS-level USB disablement is configured AND no OS-level USB restriction policies are enabled
A system is affected if it runs FACSChorus version 3.0, 3.1, 5.0, or 5.1 AND lacks both OS-enforced USB restriction policies and physical USB port controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement USB port restriction controls via operating system policies and/or deploy physical USB port blockers to prevent unauthorized device connections.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data