# CVE-2022-22765: BD Viper LT System - Hardcoded Credentials

> Attackers can use hardcoded credentials to access, modify, or delete sensitive health information in BD Viper LT systems.

- **Severity:** High 8.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4244-wg8v-q7j8

## What is CVE-2022-22765?

CVE-2022-22765 is a high-severity vulnerability in Becton Dickinson (BD) BD Viper LT System, published on 12 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BD Viper LT system, versions 2.0 and later, contains hardcoded credentials. If exploited, threat actors may be able to access, modify or delete sensitive information, including electronic protected health information (ePHI), protected health information (PHI) and personally identifiable information (PII). BD Viper LT system versions 4.0 and later utilize Microsoft Windows 10 and have additional Operating System hardening configurations which increase the attack complexity required to exploit this vulnerability.

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

## Which versions are affected by CVE-2022-22765?

It affects 1 product.


Products: Bd Viper Lt System Firmware.

## How do I fix CVE-2022-22765?

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

## Is CVE-2022-22765 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22765 and fix it if it is affected.

What it is: CVE-2022-22765 is a high-severity vulnerability in Becton Dickinson (BD) BD Viper LT System, published on 12 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22765 in the wild and no public exploit code.

Affected product: Becton Dickinson (BD) BD Viper LT System. 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-2022-22765/ (Markdown: https://insights.sbomify.com/CVE-2022-22765/index.md)
```

## Sources

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

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