CVE Vulnerabilities

CVE-2020-12039

Use of Hard-coded Password

Published: Jun 29, 2020 | Modified: Nov 21, 2024
CVSS 3.x
2.4
LOW
Source:
NVD
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

Baxter Sigma Spectrum Infusion Pumps Sigma Spectrum Infusion System vs6.x model 35700BAX & Baxter Spectrum Infusion System vs8.x model 35700BAX2 contain hardcoded passwords when physically entered on the keypad provide access to biomedical menus including device settings, view calibration values, network configuration of Sigma Spectrum WBM if installed.

Weakness

The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

Affected Software

Name Vendor Start Version End Version
Sigma_spectrum_infusion_system_firmware Baxter 6.0 (including) 6.05 (including)
Sigma_spectrum_infusion_system_firmware Baxter 8.0 (including) 8.0 (including)

Extended Description

There are two main variations of a hard-coded password:

Potential Mitigations

  • For inbound authentication: apply strong one-way hashes to your passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When receiving an incoming password during authentication, take the hash of the password and compare it to the hash that you have saved.
  • Use randomly assigned salts for each separate hash that you generate. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
  • For front-end to back-end connections: Three solutions are possible, although none are complete.

References