CVE-2022-22766 | BD Pyxis Products - Hardcoded Credentials

Hardcoded credentials are used in specific BD Pyxis products. If exploited, threat actors may be able to gain access to the underlying file system and could potentially exploit application files for information that could be used to decrypt application credentials or gain access to electronic protected health information (ePHI) or other sensitive information.

Published: 2022-02-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-22766 is rated Low Risk (33.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-22766

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-08-04 0.09% 0.05% -0.04%
2 2025-03-30 0.16% 0.09% -0.07%
3 2025-03-29 — 0.16% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-22766

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 5.9 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2022-22766

Affected software / configurations for CVE-2022-22766

Vendor Product Version Raw CPE
bd pyxis_anesthesia_station_es_firmware — cpe:2.3:o:bd:pyxis_anesthesia_station_es_firmware:*:*:*:*:*:*:*:*
bd pyxis_anesthesia_station_4000_firmware — cpe:2.3:o:bd:pyxis_anesthesia_station_4000_firmware:*:*:*:*:*:*:*:*
bd pyxis_cato_firmware — cpe:2.3:o:bd:pyxis_cato_firmware:*:*:*:*:*:*:*:*
bd pyxis_ciisafe_firmware — cpe:2.3:o:bd:pyxis_ciisafe_firmware:*:*:*:*:*:*:*:*
bd pyxis_inventory_connect_firmware — cpe:2.3:o:bd:pyxis_inventory_connect_firmware:*:*:*:*:*:*:*:*
bd pyxis_iv_prep_firmware — cpe:2.3:o:bd:pyxis_iv_prep_firmware:*:*:*:*:*:*:*:*
bd pyxis_jitrbud_firmware — cpe:2.3:o:bd:pyxis_jitrbud_firmware:*:*:*:*:*:*:*:*
bd pyxis_kanban_rf_firmware — cpe:2.3:o:bd:pyxis_kanban_rf_firmware:*:*:*:*:*:*:*:*
bd pyxis_logistics_firmware — cpe:2.3:o:bd:pyxis_logistics_firmware:*:*:*:*:*:*:*:*
bd pyxis_med_link_family_firmware — cpe:2.3:o:bd:pyxis_med_link_family_firmware:*:*:*:*:*:*:*:*
bd pyxis_medbank_firmware — cpe:2.3:o:bd:pyxis_medbank_firmware:*:*:*:*:*:*:*:*
bd pyxis_medstation_4000_firmware — cpe:2.3:o:bd:pyxis_medstation_4000_firmware:*:*:*:*:*:*:*:*
bd pyxis_medstation_es_firmware — cpe:2.3:o:bd:pyxis_medstation_es_firmware:*:*:*:*:*:*:*:*
bd pyxis_medstation_es_server_firmware — cpe:2.3:o:bd:pyxis_medstation_es_server_firmware:*:*:*:*:*:*:*:*
bd pyxis_parassist_firmware — cpe:2.3:o:bd:pyxis_parassist_firmware:*:*:*:*:*:*:*:*
bd pyxis_pharmopack_firmware — cpe:2.3:o:bd:pyxis_pharmopack_firmware:*:*:*:*:*:*:*:*
bd pyxis_procedurestation_firmware — cpe:2.3:o:bd:pyxis_procedurestation_firmware:*:*:*:*:*:*:*:*
bd pyxis_rapid_rx_firmware — cpe:2.3:o:bd:pyxis_rapid_rx_firmware:*:*:*:*:*:*:*:*
bd pyxis_stockstation_firmware — cpe:2.3:o:bd:pyxis_stockstation_firmware:*:*:*:*:*:*:*:*
bd pyxis_supplycenter_firmware — cpe:2.3:o:bd:pyxis_supplycenter_firmware:*:*:*:*:*:*:*:*
bd pyxis_supplyroller_firmware — cpe:2.3:o:bd:pyxis_supplyroller_firmware:*:*:*:*:*:*:*:*
bd pyxis_supplystation_firmware — cpe:2.3:o:bd:pyxis_supplystation_firmware:*:*:*:*:*:*:*:*
bd pyxis_track_and_deliver_firmware — cpe:2.3:o:bd:pyxis_track_and_deliver_firmware:*:*:*:*:*:*:*:*
bd rowa_pouch_packaging_systems_firmware — cpe:2.3:o:bd:rowa_pouch_packaging_systems_firmware:*:*:*:*:*:*:*:*

References for CVE-2022-22766

cvelogic Threat Intelligence