McAfee Data Loss Prevention Endpoint (DLPe) 11.6.100.41 for Windows

CPE Details

McAfee Data Loss Prevention Endpoint (DLPe) 11.6.100.41 for Windows
mcafee
data_loss_prevention_endpoint
11.6.100.41
2021-04-27
12h09 +00:00
2021-05-18
13h18 +00:00
CPE NVD
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:mcafee:data_loss_prevention_endpoint:11.6.100.41:*:*:*:*:windows:*:*

Informations

Vendor

mcafee

Product

data_loss_prevention_endpoint

Version

11.6.100.41

Target Software

windows

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2022-2330 2022-08-30 05h35 +00:00 Improper Restriction of XML External Entity Reference vulnerability in DLP Endpoint for Windows prior to 11.9.100 allows a remote attacker to cause the DLP Agent to access a local service that the attacker wouldn't usually have access to via a carefully constructed XML file, which the DLP Agent doesn't parse correctly.
6.5
Moyen
CVE-2021-31848 2021-11-01 18h25 +00:00 Cross site scripting (XSS) vulnerability in McAfee Data Loss Prevention (DLP) ePO extension prior to 11.7.100 allows a remote attacker to highjack an active DLP ePO administrator session by convincing the logged in administrator to click on a carefully crafted link in the case management part of the DLP ePO extension.
8.4
Haute
CVE-2021-31849 2021-11-01 18h25 +00:00 SQL injection vulnerability in McAfee Data Loss Prevention (DLP) ePO extension prior to 11.7.100 allows a remote attacker logged into ePO as an administrator to inject arbitrary SQL into the ePO database through the user management section of the DLP ePO extension.
8.4
Haute
CVE-2021-31844 2021-09-17 11h45 +00:00 A buffer overflow vulnerability in McAfee Data Loss Prevention (DLP) Endpoint for Windows prior to 11.6.200 allows a local attacker to execute arbitrary code with elevated privileges through placing carefully constructed Ami Pro (.sam) files onto the local system and triggering a DLP Endpoint scan through accessing a file. This is caused by the destination buffer being of fixed size and incorrect checks being made on the source size.
8.2
Haute