Security Bulletin - ePolicy Orchestrator update addresses three vulnerabilities (CVE-2021-23888, CVE-2021-23889, CVE-2021-23890)
Security Bulletins ID:
SB10352
Last Modified: 2022-05-04 19:14:34 Etc/GMT
Last Modified: 2022-05-04 19:14:34 Etc/GMT
Summary
First Published: March 25, 2021
Article contents:
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 on the Product Documentation site.
Additional steps required to address CVE-2021-23890
Apply these two settings changes after applying ePO 5.10.0 Update 10 or ePO 5.9.1 HF EPO-937000:
Setting 1: Stop auto-install of the agent into the ePO System Tree coming through the DMZ.
NOTE: The following instructions also prevent off-network/off-VPN McAfee Agents from upgrading their McAfee Agent client software.
We credit the following for responsibly reporting these flaws:
CVE-2021-23888 - Ricardo Almeida (vibrio)
CVE-2021-23889 - Michal Skowron from ING Tech Poland
CVE-2021-23890 - Saulius Pranckevičius from Danske Bank Red Team
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For ePO/server products:
Use the following instructions for server-based products:
CVSS, or Common Vulnerability Scoring System, 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 at: https://www.first.org/cvss/.
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 do not 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: |
| ePolicy Orchestrator (ePO) | 5.10 prior to Update 10 5.9.1 prior to HF EPO-937000 |
CVE-2021-23888 | CWE-938: Unvalidated Redirects and Forwards | Medium | 6.3 / 5.7 |
| CVE-2021-23889 | CWE 79: Cross-Site Scripting (XSS) | Low | 3.5 / 3.2 | ||
| CVE-2021-23890 | CWE-717: Information Leak/Disclosure | Medium | 6.5 / 5.9 | ||
| Recommendations: | Install or update to the versions listed below:
|
||||
| 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
- Additional steps required to address CVE-2021-23890
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
- CVE-2021-23888
Unvalidated client-side URL redirect vulnerability in ePolicy Orchestrator (ePO) prior to 5.10 Update 10 could cause an authenticated ePO user to load an untrusted site in an ePO iframe which could steal information from the authenticated user.
This would require the attacker to convince the ePO user to click a malicious link whilst logged into the ePO server through the same browser they clicked on the malicious link in. The results of this attack are not stored in ePO.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-23888
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23888
- CVE-2021-23889
Cross-Site Scripting vulnerability in McAfee ePolicy Orchestrator (ePO) prior to 5.10 Update 10 allows ePO administrators to inject arbitrary web script or HTML via multiple parameters where the administrator's entries were not correctly sanitized.
To exploit this the attacker would either:- Need to know an existing registered command in the ePO system which they can pass parameters to, triggering the Cross-site scripting vulnerability
- Add a new registered command to the ePO system which does not sanitize parameters. Adding a new command to the ePO system requires administrator privileges and they must be logged onto the local ePO system, not through the User Interface. This could then be exploited by a another ePO user. Execution of these commands is not granted by default to non-administrator ePO users.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23889
- CVE-2021-23890
Information leak vulnerability in the Agent Handler of ePolicy Orchestrator (ePO) prior to 5.10 Update 10 allows an unauthenticated user to download product packages (specifically McAfee Agent) available in ePO repository and install them on their own machines to have it managed and then in turn get policy details from the ePO server. This can only happen when the ePO Agent Handler is installed in a Demilitarized Zone (DMZ) to service machines not connected to the network through a VPN.
Once the software fix has been applied, further configuration changes are required. See the Additional steps required to address CVE-2021-23890 section below.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-23890
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23890
To remediate this issue:
- Customers using ePO 5.10 should update to ePO 5.10.0 Update 10.
- Customers using ePO 5.9.x and earlier should upgrade to ePO 5.10.0 Update 10.
- Customers using ePO 5.9.x and earlier could apply ePO 5.9.1 HF EPO-937000 to resolve only CVE-2021-23890. We strongly recommend upgrading ePO to version 5.10 as the End of Life for ePO 5.9.1 has been announced as August 31, 2021. For more information, see: KB93286 - End of Life for ePolicy Orchestrator 5.9.x.
| Product | Version | Type | File Name | Release Date |
| ePO | 5.9.1 | Hotfix | EPO-937000 | March 25, 2021 |
| ePO | 5.10.0 | Update | ePO 5.10.0 Update 10 | March 25, 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 on the Product Documentation site.
Additional steps required to address CVE-2021-23890
Apply these two settings changes after applying ePO 5.10.0 Update 10 or ePO 5.9.1 HF EPO-937000:
Setting 1: Stop auto-install of the agent into the ePO System Tree coming through the DMZ.
- On the remote ePO Agent Handler that is installed in a DMZ, navigate to the
Agent Handler\DB folder. - Edit the
server.ini configuration file. - Add the setting DMZ=1 under the [Server] section and save the file.
NOTE: The following instructions also prevent off-network/off-VPN McAfee Agents from upgrading their McAfee Agent client software.
- On the remote ePO Agent Handler that is installed in a DMZ, navigate to the
apache2\conf folder. - Open the
httpd.conf file. - Search for this line:
<Location /redir/mepo> require all denied </location> - Add the following contents to below the location found in the previous step 3.
# Block agent package requests from being served by this agent handler
<LocationMatch "/Software/(?i)(Current|Previous|Evaluation)/EPOAGENT(.*)">
SetHandler none
Require all denied
</LocationMatch>
- Save the
httpd.conf file. - Open Service Control Manager and restart the ePO 5.10 Server service.
We credit the following for responsibly reporting these flaws:
CVE-2021-23888 - Ricardo Almeida (vibrio)
CVE-2021-23889 - Michal Skowron from ING Tech Poland
CVE-2021-23890 - Saulius Pranckevičius from Danske Bank Red Team
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For ePO/server products:
Use the following instructions for server-based products:
- Check the version and build of ePO that is installed. For instructions, see KB52634 - How to determine what update is installed for ePO.
- Create a query in ePO for the product version of the product installed within your organization.
CVSS, or Common Vulnerability Scoring System, 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 at: https://www.first.org/cvss/.
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 do not 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-23888: ePO unvalidated URL redirect vulnerability
Base Score 6.3 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) Low (L) User Interaction (UI) Required (R) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 5.7 Exploitability (E) Proof of Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N/E:P/RL:O/RC:C&version=3.1
- CVE-2021-23889: ePO Cross-site Scripting vulnerability
Base Score 3.5 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) High (H) User Interaction (UI) Required (R) Scope (S) Unchanged (U) Confidentiality (C) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 3.2 Exploitability (E) Proof of Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C&version=3.1
- CVE-2021-23890: ePO Information Leak vulnerability
Base Score 6.5 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) None (N) User Interaction (UI) None (N) Scope (S) Unchanged (U) Confidentiality (C) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 5.9 Exploitability (E) Proof of Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C&version=3.1
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.
