dbcve.org
FacschorusApplication · Bd

CVE-2023-29061

MEDIUM · 5.2 CVSS v3.1 Published 2023-11-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
There is no BIOS password on the FACSChorus workstation. A threat actor with physical access to the workstation can potentially exploit this vulnerability to access the BIOS configuration and modify the drive boot order and BIOS pre-boot authentication.

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 · high confidence

The FACSChorus workstation has no BIOS password protection configured. An attacker with physical access can access the BIOS configuration utility during boot, allowing modification of the drive boot order and disabling or altering BIOS pre-boot authentication settings.

MitigationConfigure a strong BIOS password on the FACSChorus workstation to prevent unauthorized access to BIOS settings and protect boot order configuration.

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
FacschorusApplication
Affected:= 5.0= 5.1= 3.0= 3.1

CVSS 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
None
Integrity
Low
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FACSChorus software version
    On the FACSChorus workstation, open the FACSChorus application or check the installed programs list. Look for the version number of Bd FACSChorus software.
    Affected if The installed version is exactly 5.0, 5.1, 3.0, or 3.1
  2. Confirm BIOS password is not set via physical access
    During workstation boot, press the appropriate key (typically Delete, F2, or F12) to enter the BIOS/UEFI configuration utility. Navigate to the Security or Password settings section.
    Affected if No BIOS password (administrator or user password) is configured, or the BIOS password field appears empty or disabled
  3. Check BIOS password status via hardware management interface
    If the workstation has a remote management card (BMC/IPMI/iLO), access it via web interface or IP. Look for BIOS security settings or password status in the hardware management console.
    Affected if The remote management interface shows no BIOS password configured or indicates BIOS password protection is disabled
  4. Verify boot order protection status
    In the BIOS/UEFI configuration utility, navigate to Boot options or Boot Order settings.
    Affected if Boot order can be modified without requiring a password, or no boot password is set

A user is affected if the FACSChorus workstation runs version 3.0, 3.1, 5.0, or 5.1 AND has no BIOS password configured, allowing unauthorized modification of boot settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure a strong BIOS password on the FACSChorus workstation to prevent unauthorized access to BIOS settings and protect boot order configuration.

Recommended fix Moderate confidence
  1. Power on or restart the FACSChorus workstation and access the BIOS setup utility (typically by pressing Del, F2, or F12 during boot)
  2. Navigate to the Security or Password settings section within the BIOS menu
  3. Set a strong BIOS administrator password following vendor complexity requirements
  4. Save the BIOS configuration changes and exit (typically pressing F10)
  5. Verify that the BIOS password is required on next reboot before accessing BIOS setup or boot options
  6. Configure BIOS pre-boot authentication to require password for any boot order changes or hardware configuration modifications
  7. Restrict physical access to the workstation to authorized personnel only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Facschorus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29061 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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