CVE-2022-22765
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 · uneditedBD 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.
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 confidenceThe BD Viper LT system contains hardcoded credentials in versions 2.0 and later that could allow unauthorized access to the system. If exploited, threat actors may access, modify, or delete sensitive health information including ePHI, PHI, and PII. Versions 4.0 and later utilize Microsoft Windows 10 with additional Operating System hardening configurations that increase the attack complexity required to exploit this vulnerability.
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>= 2.0, < 4.80CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify BD Viper LT firmware versionAccess the system administration interface or diagnostic menu to view the current firmware version. This is typically found in system settings, about section, or via a version query command accessible to authorized administrators.Affected if The displayed firmware version is 2.0 or higher but below 4.80
-
Confirm hardcoded credentials are presentReview system documentation or audit configuration files for account credentials. The vulnerability involves default or embedded credentials that ship with the system.Affected if Default, hardcoded, or embedded credentials exist in the system configuration or are documented in administrative guides
-
Verify network accessibility of authentication interfaceDetermine if the system's remote authentication or management interfaces are exposed to network access. Check firewall rules, network segmentation, and interface bindings.Affected if The authentication or management interface is reachable from network segments beyond isolated administrativevlans
The environment is affected if the BD Viper LT system runs firmware version 2.0 or higher but below 4.80 and has accessible interfaces that could use the hardcoded credentials for unauthorized access.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped4.80
Upgrade to BD Viper LT version 4.0 or later which includes Windows 10 with OS hardening; if upgrade is not feasible, implement compensating controls such as network segmentation, access monitoring, and isolation from broader networks.
Viper Lt System Firmware >= 4.80
- Contact BD (Becton, Dickinson and Company) technical support to obtain the firmware upgrade to version 4.80 or later
- Follow BD's documented firmware update procedure for the Viper LT system
- After updating, verify the system is running firmware version 4.80 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
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 locallyCheck whether your project pulls in CVE-2022-22765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22765 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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