Fresenius Kabi Vigilant Software Suite 2.0.1.3 risky encryption

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.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in Fresenius Kabi Vigilant Software Suite 2.0.1.3. This vulnerability affects unknown code. The manipulation results in risky encryption. This vulnerability is identified as CVE-2021-33846. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Fresenius Kabi Vigilant Software Suite 2.0.1.3. It has been classified as problematic. Affected is an unknown function. The manipulation with an unknown input leads to a risky encryption vulnerability. CWE is classifying the issue as CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. This is going to have an impact on confidentiality.

The weakness was released 01/22/2022 as icsma-21-355-01. The advisory is shared for download at cisa.gov. This vulnerability is traded as CVE-2021-33846 since 11/30/2021. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.1
VulDB Meta Temp Score: 4.1

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

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

CVSSv2info

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

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

Exploitinginfo

Class: Risky encryption
CWE: CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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-33846 (🔍)
GCVE (CVE): GCVE-0-2021-33846
GCVE (VulDB): GCVE-100-191436

Entryinfo

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

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!