CVE-2019-6517 json
BD FACSLyric Research Use Only, Windows 10 Professional Operating System, U.S.
published 2019-02-06 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16076
- cvss
- 6.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSMA-19-029-02 updated cvss 6.8
BD FACSLyric (Update A)
-
Becton, Dickinson and Company (BD) FACSLyric IVD Windows 10 Professional Operating System U.S. release Becton, Dickinson and Company (BD) FACSLyric Research Use Only Windows 10 Professional Operating System, U.S. and Malaysian Releases, between November 2017 and Novaffected: vendor fix bd.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- ICS-CERT BD FACSLyric
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
securityfocus.com
/bid/106766
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSMA-19-029-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-6517
- NVD CVE-2019-6517
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.