CVE-2022-22767
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 · uneditedSpecific BD Pyxis™ products were installed with default credentials and may presently still operate with these credentials. There may be scenarios where BD Pyxis™ products are installed with the same default local operating system credentials or domain-joined server(s) credentials that may be shared across product types. If exploited, threat actors may be able to gain privileged access to the underlying file system and could potentially exploit or gain access to ePHI or other sensitive information.
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 · high confidenceBD Pyxis medication dispensing products were shipped and potentially deployed with hardcoded default local operating system and/or domain credentials. These shared default credentials across product types allow unauthenticated threat actors to gain privileged filesystem access and potentially exfiltrate ePHI or other sensitive healthcare data.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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.
-
Inventory BD Pyxis devices in your environmentIdentify all deployed BD Pyxis medication dispensing products (Anesthesia Station ES, CIIsafe, Logistics, Medbank, Medstation 4000, Medstation ES, Medstation ES Server, Parassist) and document their firmware versions and network locations.Affected if Any BD Pyxis device from the affected product list is deployed and default credentials have not been explicitly changed from factory settings.
-
Verify default credentials have been changedLocate the device management interface or console and confirm that local OS and domain credentials have been changed from any default or factory settings. Check credential management records if available.Affected if Default credentials remain unchanged on any affected device, allowing potential unauthenticated access.
-
Review authentication logs for unauthorized accessExamine device and domain authentication logs for any login attempts using default or unknown credentials, particularly from unexpected IP addresses or at unusual times.
-
Check for unauthorized filesystem accessReview filesystem access logs and audit trails on Pyxis devices for any privileged access to directories containing patient data or ePHI that was not initiated by authorized personnel.
-
Inspect network segmentation and access controlsVerify network segmentation controls around Pyxis devices and check whether the devices are accessible from untrusted network segments without authentication.Affected if Pyxis devices are accessible from network segments outside the trusted medical device zone without requiring credential authentication.
You are affected if any BD Pyxis device from the affected product list still uses default credentials that have not been changed from factory settings, or if evidence exists of unauthorized access using default credential patterns.
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.
From vendor dataImmediately change all default credentials on affected BD Pyxis devices to unique, strong passwords per device, audit for any unauthorized access, and implement a credential management policy to prevent future use of default credentials.
- Consultation12.0 h
- Implementation24.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 $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22767 — 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-22767 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