# CVE-2017-6022: Hardcoded credentials in BD Kiestra PerformA and KLA Journal Service

> Hard-coded passwords in BD PerformA and KLA Journal Service allow attackers to access the BD Kiestra Database and view sensitive patient information.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8q2j-7m4j-w338

## What is CVE-2017-6022?

CVE-2017-6022 is a critical vulnerability in BD Kiestra PerformA and KLA Journal Service, published on 30 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2017-6022?

It affects 2 products.


Products: Bd Kla Journal Service, Bd Performa.

## How do I fix CVE-2017-6022?

No fix has been published for CVE-2017-6022 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6022 being exploited?

There is no known exploitation of CVE-2017-6022 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6022 and fix it if it is affected.

What it is: CVE-2017-6022 is a critical vulnerability in BD Kiestra PerformA and KLA Journal Service, published on 30 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6022 in the wild and no public exploit code.

Affected product: BD Kiestra PerformA and KLA Journal Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6022/ (Markdown: https://insights.sbomify.com/CVE-2017-6022/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6022
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6022
- OSV: https://osv.dev/vulnerability/CVE-2017-6022

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6022/
Summaries are generated and may contain mistakes; the official description above is the record.