Bromium Client up to 4.0.3.2059/4.1.7 race condition

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

Summaryinfo

A vulnerability, which was classified as problematic, was found in Bromium Client up to 4.0.3.2059/4.1.7. This impacts an unknown function. Executing a manipulation can lead to race condition. This vulnerability is registered as CVE-2019-18567. The attack needs to be launched locally. No exploit is available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability has been found in Bromium Client up to 4.0.3.2059/4.1.7 and classified as problematic. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect availability. CVE summarizes:

Bromium client version 4.0.3.2060 and prior to 4.1.7 Update 1 has an out of bound read results in race condition causing Kernel memory leaks or denial of service. Versions prior to

The weakness was published 02/03/2020 (Website). The advisory is shared for download at support.bromium.com. This vulnerability was named CVE-2019-18567 since 10/28/2019. The attack needs to be approached locally. A single authentication is required for exploitation. There are neither technical details nor an exploit publicly available.

Applying the patch 4.1.7 Update 1 is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.2
VulDB Meta Temp Score: 5.1

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.1
NVD Vector: 🔍

CNA Base Score: 6.1
CNA Vector (Airbus): 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
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: Patch
Status: 🔍

0-Day Time: 🔍

Patch: 4.1.7 Update 1

Timelineinfo

10/28/2019 🔍
02/03/2020 +98 days 🔍
02/04/2020 +1 days 🔍
03/28/2024 +1514 days 🔍

Sourcesinfo

Advisory: support.bromium.com
Status: Not defined

CVE: CVE-2019-18567 (🔍)
GCVE (CVE): GCVE-0-2019-18567
GCVE (VulDB): GCVE-100-149620

Entryinfo

Created: 02/04/2020 08:36
Updated: 03/28/2024 01:04
Changes: 02/04/2020 08:36 (39), 02/04/2020 08:41 (11), 03/28/2024 01:04 (34)
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 ▸

Do you need the next level of professionalism?

Upgrade your account now!