title: Fresenius Kabi Agilia Connect Infusion System plaintext storage of a password
description: An attacker with physical access to the host can extract the secrets from the registry and create valid JWT tokens for the Fresenius Kabi Vigilant MasterMed version 2.0.1.3 application and impersonate arbitrary users. An attacker could manipulate RabbitMQ queues and messages by impersonating users.
problem types: CWE-256 Plaintext Storage of a Password
affected:
{
product: Vigilant Software Suite (Mastermed Dashboard)
vendor: Fresenius Kabi
versions:
lessThan: 2.0.1.3, status: affected, version: unspecified, versionType: custom
}
{
product: Agilia Partner
vendor: Fresenius Kabi
versions:
lessThan: 3.0, status: affected, version: unspecified, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: LOCAL
availabilityImpact: NONE
baseScore: 6.5
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: NONE
privilegesRequired: LOW
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
version: 3.1
]
solutions: Fresenius Kabi has created new versions to address these vulnerabilities:
•	Link+ v3.0 (D16 or later)
•	VSS v1.0.3 (or later)
•	Agilia Connect Pumps Wifi Module (D29 or later)
•	Agilia Connect Partner v3.3.2 (or later)
Fresenius Kabi has initiated communication on this topic in April 2021 with customers to inform them about availability of the new versions in corresponding countries. Contact Fresenius Kabi online or by phone at 1-800-333-6925 for more information on updating to the newest version.
Fresenius Kabi also identified that early Link+ devices (approximatively 1200 devices) would need hardware change to support D16 or later firmware. Until those devices can be replaced in customers’ installation, Fresenius Kabi recommends users to rely on CISA recommendation.
workarounds: CISA recommends users take defensive measures to minimize the risk of exploitation of these vulnerabilities. Specifically, users should:
•	Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from the Internet.
•	Locate control system networks and remote devices behind firewalls and isolate them from the business network.
•	When remote access is required, use secure methods, such as virtual private networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as its connected devices.