McAfee Data Loss Prevention up to 11.3.2 on Windows Message memory corruption

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in McAfee Data Loss Prevention up to 11.3.2 on Windows. Affected is an unknown function. The manipulation as part of Message leads to memory corruption. This vulnerability is traded as CVE-2019-3634. It is possible to launch the attack on the local host. There is no exploit available. It is recommended to upgrade the affected component. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as critical, has been found in McAfee Data Loss Prevention up to 11.3.2 on Windows (Data Loss Prevention Software). This issue affects some unknown processing. The manipulation as part of a Message leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in McAfee Data Loss Prevention (DLPe) for Windows 11.x prior to 11.3.2.8 allows local user to cause the Windows operating system to "blue screen" via an encrypted message sent to DLPe which when decrypted results in DLPe reading unallocated memory.
The weakness was presented 08/21/2019 (Website). The advisory is shared at kc.mcafee.com. The identification of this vulnerability is CVE-2019-3634 since 01/03/2019. An attack has to be approached locally. Required for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 11.3.2.8 eliminates this vulnerability.
See VDB-117791 and VDB-140572 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 6.6
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 4.4
CNA Vector (Trellix): 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Data Loss Prevention 11.3.2.8
Timeline
01/03/2019 🔍08/21/2019 🔍
08/22/2019 🔍
11/28/2023 🔍
Sources
Vendor: mcafee.comAdvisory: kc.mcafee.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-3634 (🔍)
GCVE (CVE): GCVE-0-2019-3634
GCVE (VulDB): GCVE-100-140573
See also: 🔍
Entry
Created: 08/22/2019 09:59Updated: 11/28/2023 13:37
Changes: 08/22/2019 09:59 (60), 08/02/2020 18:44 (1), 11/28/2023 13:37 (14)
Complete: 🔍
Cache ID: 216:34D:103
No comments yet. Languages: en.
Please log in to comment.