Security Bulletin - Data Loss Prevention ePO extension update fixes two vulnerabilities (CVE-2021-31848 and CVE-2021-31849)
Security Bulletins ID:
SB10371
Last Modified: 2022-05-04 19:32:38 Etc/GMT
Last Modified: 2022-05-04 19:32:38 Etc/GMT
Summary
First Published: October 29, 2021
Article contents:
This update is required for all customers using our Enterprise DLP products. The extension is common to:
To remediate this issue:
Download and Installation Instructions
For instructions to download product updates and hotfixes, see: KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Acknowledgments
We credit SCRT Research Lab for responsibly reporting these flaws.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For DLP Endpoint ePO Extension:
Use the following instructions:
Common Vulnerability Scoring System (CVSS) is the result of the National Infrastructure Advisory Council's effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.
When calculating CVSS scores, we've adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We don’t factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
All Security Bulletins are published on our Knowledge Center. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
We only publish Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't allow the exclusion or limitation of liability for consequential or incidental damages, so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren't a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remain at our sole discretion and may be changed or canceled at any time.
| Product: | Impacted Versions: | CVE ID: | Impact of Vulnerabilities: | Severity Ratings: | CVSS v3.1 Base/Temporal Scores: |
| Data Loss Prevention (DLP) ePO extension | Prior to 11.7.100 and 11.6.400 | CVE-2021-31848 | CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | High | 8.4 / 7.6 |
| DLP ePO extension |
Prior to 11.7.100 and 11.6.400 | CVE-2021-31849 | CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | High | 8.4 / 7.6 |
| Recommendations: | Install or update to DLP ePO extension 11.6.400 or 11.7.100 | ||||
| Security Bulletin Replacement: | None | ||||
| Location of updated software: | Product Downloads site | ||||
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Article contents:
- Vulnerability Description
- Remediation
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
This update is required for all customers using our Enterprise DLP products. The extension is common to:
- DLP Endpoint for Windows and Mac
- DLP Discover
- DLP Prevent
- DLP Monitor
- CVE-2021-31848
Cross site scripting (XSS) vulnerability in McAfee Data Loss Prevention (DLP) ePO extension 11.7.x prior to 11.7.100 or 11.6.x prior to 11.6.400 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.
NVD CVE-2021-31848
MITRE CVE-2021-31848
- CVE-2021-31849
SQL injection vulnerability in McAfee Data Loss Prevention (DLP) ePO extension 11.7.x prior to 11.7.100 or 11.6.x prior to 11.6.400 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.
NVD CVE-2021-31849
MITRE CVE-2021-31849
To remediate this issue:
- Customers on DLP ePO extension 11.7.x should update to DLP ePO extension 11.7.100.
- Customers on DLP ePO extension 11.6.x should update to DLP ePO extension 11.6.400.
| Product | Version | Type | Release Date |
| DLP ePO extension | 11.7.100 | Update | October 29, 2021 |
| DLP ePO extension | 11.6.400 | Update | October 29, 2021 |
Download and Installation Instructions
For instructions to download product updates and hotfixes, see: KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Acknowledgments
We credit SCRT Research Lab for responsibly reporting these flaws.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For DLP Endpoint ePO Extension:
Use the following instructions:
- Log on to the ePO server.
- Click Menu, Data Protection, DLP Policy.
- Inside the DLP console click Help, About. The product version displays.
Common Vulnerability Scoring System (CVSS) is the result of the National Infrastructure Advisory Council's effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.
When calculating CVSS scores, we've adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We don’t factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
- CVE-2021-31848: XSS in DLP ePO extension case management
Base Score 8.4 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) High (H) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 7.6 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: This CVSS version 3.1 vector was used to generate this score.
- CVE-2021-31849: SQL injection vulnerability in DLP ePO extension user management
Base Score 8.4 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) High (H) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 7.6 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: This CVSS version 3.1 vector was used to generate this score.
All Security Bulletins are published on our Knowledge Center. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
We only publish Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.
- If you are a registered user, type your User ID and Password, and then click Log In.
- If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't allow the exclusion or limitation of liability for consequential or incidental damages, so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren't a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remain at our sole discretion and may be changed or canceled at any time.
