Fresenius Kabi Vigilant MasterMed 2.0.1.3 credentials storage

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.3$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Fresenius Kabi Vigilant MasterMed 2.0.1.3. Impacted is an unknown function. This manipulation causes credentials storage. The identification of this vulnerability is CVE-2021-23207. It is feasible to perform the attack on the physical device. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic was found in Fresenius Kabi Vigilant MasterMed 2.0.1.3. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a credentials storage vulnerability. The CWE definition for the vulnerability is CWE-256. Storing a password in plaintext may result in a system compromise. As an impact it is known to affect confidentiality.

The weakness was shared 01/22/2022 as icsma-21-355-01. The advisory is shared at cisa.gov. This vulnerability is known as CVE-2021-23207 since 11/30/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3

VulDB Base Score: 2.1
VulDB Temp Score: 2.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (ICS-CERT): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Credentials storage
CWE: CWE-256 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/30/2021 🔍
01/22/2022 +53 days 🔍
01/22/2022 +0 days 🔍
01/27/2022 +5 days 🔍

Sourcesinfo

Advisory: icsma-21-355-01
Status: Not defined

CVE: CVE-2021-23207 (🔍)
GCVE (CVE): GCVE-0-2021-23207
GCVE (VulDB): GCVE-100-191449

Entryinfo

Created: 01/22/2022 08:47
Updated: 01/27/2022 14:05
Changes: 01/22/2022 08:47 (47), 01/27/2022 14:05 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!