BeyondTrust AppGuard Enterprise up to 6.6.20.2 temp file

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

Summaryinfo

A vulnerability was found in BeyondTrust AppGuard Enterprise up to 6.6.20.2. It has been classified as critical. Affected by this issue is some unknown functionality. This manipulation causes temp file. The identification of this vulnerability is CVE-2021-42255. There is no exploit available.

Detailsinfo

A vulnerability classified as critical was found in BeyondTrust AppGuard Enterprise up to 6.6.20.2. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a temp file vulnerability. The CWE definition for the vulnerability is CWE-377. Creating and using insecure temporary files can leave application and system data vulnerable to attack. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was shared 04/13/2022 as MNDT-2022-0022. The advisory is shared at github.com. This vulnerability is known as CVE-2021-42255 since 10/11/2021. Neither technical details nor an exploit are publicly available.

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

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Temp file
CWE: CWE-377
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

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

10/11/2021 🔍
04/13/2022 +184 days 🔍
04/13/2022 +0 days 🔍
04/19/2022 +6 days 🔍

Sourcesinfo

Advisory: MNDT-2022-0022
Status: Not defined

CVE: CVE-2021-42255 (🔍)
GCVE (CVE): GCVE-0-2021-42255
GCVE (VulDB): GCVE-100-197209

Entryinfo

Created: 04/13/2022 10:09
Updated: 04/19/2022 07:41
Changes: 04/13/2022 10:09 (37), 04/19/2022 07:41 (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!