What is the severity of CVE-2017-6022?

CVE-2017-6022 is classified as a high severity vulnerability due to the use of hard-coded passwords.

How do I fix CVE-2017-6022?

To fix CVE-2017-6022, update to versions of BD PerformA later than 2.0.14.0 and BD KLA Journal Service later than 1.0.51.

What software is affected by CVE-2017-6022?

CVE-2017-6022 affects BD PerformA versions up to 2.0.14.0 and KLA Journal Service versions up to 1.0.51.

What is the impact of exploiting CVE-2017-6022?

Exploiting CVE-2017-6022 could allow an attacker to gain unauthorized access to the BD Kiestra Database.

Who is responsible for the CVE-2017-6022 vulnerability?

The vulnerability CVE-2017-6022 was discovered in products developed by Becton, Dickinson and Company.

Vulnerability/
CVE-2017-6022

critical

9.8

CWE

798 259

30/6/2017

5/8/2024

CVE-2017-6022

First published: Fri Jun 30 2017(Updated: )

A hard-coded password issue was discovered in Becton, Dickinson and Company (BD) PerformA, Version 2.0.14.0 and prior versions, and KLA Journal Service, Version 1.0.51 and prior versions. They use hard-coded passwords to access the BD Kiestra Database, which could be leveraged to compromise the confidentiality of limited PHI/PII information stored in the BD Kiestra Database.

Credit: ics-cert@hq.dhs.gov

Affected Software	Affected Version	How to fix
Bd Performa	<=2.0.14.0
Bd Kla Journal Service	<=1.0.51

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-6022?
CVE-2017-6022 is classified as a high severity vulnerability due to the use of hard-coded passwords.
How do I fix CVE-2017-6022?
To fix CVE-2017-6022, update to versions of BD PerformA later than 2.0.14.0 and BD KLA Journal Service later than 1.0.51.
What software is affected by CVE-2017-6022?
CVE-2017-6022 affects BD PerformA versions up to 2.0.14.0 and KLA Journal Service versions up to 1.0.51.
What is the impact of exploiting CVE-2017-6022?
Exploiting CVE-2017-6022 could allow an attacker to gain unauthorized access to the BD Kiestra Database.
Who is responsible for the CVE-2017-6022 vulnerability?
The vulnerability CVE-2017-6022 was discovered in products developed by Becton, Dickinson and Company.

collector/nvd-index
agent/weakness
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/tags
agent/severity
agent/event
agent/description
agent/first-publish-date
agent/source
vendor/bd
canonical/bd performa
version/bd performa/2.0.14.0
canonical/bd kla journal service
version/bd kla journal service/1.0.51

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-6022?
CVE-2017-6022 is classified as a high severity vulnerability due to the use of hard-coded passwords.
How do I fix CVE-2017-6022?
To fix CVE-2017-6022, update to versions of BD PerformA later than 2.0.14.0 and BD KLA Journal Service later than 1.0.51.
What software is affected by CVE-2017-6022?
CVE-2017-6022 affects BD PerformA versions up to 2.0.14.0 and KLA Journal Service versions up to 1.0.51.
What is the impact of exploiting CVE-2017-6022?
Exploiting CVE-2017-6022 could allow an attacker to gain unauthorized access to the BD Kiestra Database.
Who is responsible for the CVE-2017-6022 vulnerability?
The vulnerability CVE-2017-6022 was discovered in products developed by Becton, Dickinson and Company.