dbcve.org
FacslyricOperating system · Bd

CVE-2019-6517

MEDIUM · 6.8 CVSS v3.1 Published 2019-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
BD FACSLyric Research Use Only, Windows 10 Professional Operating System, U.S. and Malaysian Releases, between November 2017 and November 2018 and BD FACSLyric IVD Windows 10 Professional Operating System US release does not properly enforce user access control to privileged accounts, which may allow for unauthorized access to administrative level functions.

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 confidence

The BD FACSLyric flow cytometry system (both Research Use Only and IVD variants) running Windows 10 Professional fails to properly enforce user access controls for privileged accounts, potentially allowing unauthorized users to escalate privileges and access administrative-level functions that should be restricted.

MitigationApply vendor-supplied patches from BD and implement proper role-based access control (RBAC) configurations to ensure administrative functions are only accessible to authorized users. Coordinate with BD for medical device regulatory compliance requirements.

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
FacslyricOperating system
Affected:all versions
Facslyric IvdOperating system
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm BD FACSLyric system presence
    Identify if your facility uses a BD FACSLyric flow cytometry instrument - check hardware inventory, instrument labeling, or BD software installation (FACSLyric software)
    Affected if You have a BD FACSLyric or BD FACSLyric IVD flow cytometry system in your environment
  2. Verify Windows 10 Professional operating system
    On the instrument workstation, open Command Prompt or PowerShell and run: systeminfo | findstr /B /C:"OS Name" /C:"OS Version" - or check System Properties
    Affected if The system is running Windows 10 Professional (the vulnerability applies specifically to this OS configuration)
  3. Check user account types and group memberships
    Open Computer Management > Local Users and Groups > Groups. Review members of Administrators, Power Users, and Users groups. Run: net user on the instrument workstation
    Affected if Non-administrative users have been added to privileged groups (Administrators, Power Users) or have been granted admin-level permissions they should not have
  4. Inspect local security policy access controls
    Run secpol.msc or gpedit.msc on the instrument workstation. Navigate to Local Policies > User Rights Assignment. Review who can: Access this computer from the network, Allow log on locally, Shut down the system, and Manage auditing and security log
    Affected if Non-privileged users have been granted additional user rights that should be restricted to administrators only
  5. Verify application-level access restrictions
    Check BD FACSLyric software configuration for any user role settings, admin function protections, or RBAC configurations within the BD software itself (consult BD documentation for software-specific settings)
    Affected if Administrative functions within the BD FACSLyric software are accessible to standard/non-privileged user accounts

Your environment is affected if you operate a BD FACSLyric or BD FACSLyric IVD system running Windows 10 Professional where non-administrative users can access privileged functions or have been granted elevated Windows permissions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches from BD and implement proper role-based access control (RBAC) configurations to ensure administrative functions are only accessible to authorized users. Coordinate with BD for medical device regulatory compliance requirements.

Fix this in Facslyric Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6517 — 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-2019-6517 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