CVE-2022-0842: Security Bulletin - ePolicy Orchestrator update addresses multiple product vulnerabilities (CVE-2022-0842, CVE-2022-0857, CVE-2022-0858, CVE-2022-0859, CVE-2022-0861, CVE-2022-0862) and updates Java,

First Published: March 22, 2022

Product:

Impacted Versions:

CVE ID:

Impact of Vulnerabilities:

Severity Ratings:

CVSS v3.1
Base/Temporal Scores:

ePolicy Orchestrator (ePO)

5.10 prior to CU 13

CVE-2022-0842

CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)

Medium

5.4 / 4.9

CVE-2022-0857

CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)

Medium

5.4 / 4.9

CVE-2022-0858

CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)

Medium

4.3 / 3.9

CVE-2022-0859

CWE-522: Insufficiently Protected Credentials

Medium

6.5 / 5.9

CVE-2022-0861

CWE-611: Improper Restriction of XML External Entity Reference

Low

3.5 / 3.2

CVE-2022-0862

CWE-522: Insufficiently Protected Credentials

Low

3.1 / 2.8

Tomcat CVE-2021-42340

CWE-772: Missing Release of Resource after Effective Lifetime

Medium

5.3 / 4.8

Apache HTTP Server CVE-2021-34798

Apache HTTP Server
CVE-2020-13938

CWE-476: NULL Pointer Dereference

CWE-862: Missing Authorization

High

Medium

7.5

5.5

Java multiple CVEs

See Java CVEs Security Advisory link below.

Recommendations:

Install or update to ePO 5.10.0 CU 13.

Security Bulletin Replacement:

None

Location of updated software:

Product Downloads site

To receive email notification when this Security Bulletin 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

Vulnerability Description
This release addresses one blind SQL injection vulnerability in ePO and updates three libraries used by ePO.

Below are the third-party libraries updated in this release, along with details about CVEs that impacted ePO.

1. Java has been updated to the January 2022 update.

   Reference: Java SE Risk Matrix

2. Apache HTTP Server has been updated to 2.4.51 from 2.4.38.
   CVE-2021-34798
   CVE-2020-13938

   Reference: Apache HTTP Server 2.4 vulnerabilities
   For other Apache HTTP Server CVE responses for ePO, see: KB94982 - ePolicy Orchestrator documentation for Apache CVEs.

3. Tomcat has been updated to 9.0.54 from 9.0.52.
   CVE-2021-42340

   Reference: Tomcat 9.x vulnerabilities

McAfee Enterprise code vulnerabilities

1. CVE-2022-0842
   A blind SQL injection vulnerability in McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote authenticated attacker to potentially obtain information from the ePO database. The data obtained is dependent on the privileges the attacker has and to obtain sensitive data the attacker would require administrator privileges.
   NIST CVE-2022-0842
   MITRE CVE-2022-0842

2. CVE-2022-0857
   A reflected cross-site scripting (XSS) vulnerability in McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote attacker to potentially obtain access to an ePO administrator’s session by convincing the attacker to click on a carefully crafted link. This would lead to limited access to sensitive information and limited ability to alter some information in ePO due to the area of the User Interface the vulnerability is present in.
   NIST CVE-2022-0857
   MITRE CVE-2022-0857

3. CVE-2022-0858
   A cross-site scripting (XSS) vulnerability in McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote attacker to potentially obtain access to an ePO administrator’s session by convincing the attacker to click on a carefully crafted link. This would lead to limited ability to alter some information in ePO due to the area of the User Interface the vulnerability is present in.
   NIST CVE-2022-0858
   MITRE CVE-2022-0858

4. CVE-2022-0859
   McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a local attacker to point an ePO server to an arbitrary SQL server during the restoration of the ePO server. To achieve this the attacker would have to be logged onto the server hosting the ePO server (restricted to administrators) and to know the SQL server password.

   Although this is rated as a relatively high CVSS, McAfee Enterprise does not expect this to be a common scenario as both credentials are expected to be known only to a few members of staff and the attacker must have access to the system hosting the ePO server.
   NIST CVE-2022-0859
   MITRE CVE-2022-0859

5. CVE-2022-0861
   A XML Extended entity vulnerability in McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote administrator attacker to upload a malicious XML file through the extension import functionality. The impact is limited to some access to confidential information and some ability to alter data.

   Should the remote attacker already have administrator privileges they are likely to be able to perform other malicious activities which exceed the impact of this issue.
   NIST CVE-2022-0861
   MITRE CVE-2022-0861

6. CVE-2022-0862
   A lack of password change protection vulnerability in a depreciated API of McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote attacker to change the password of a compromised session without knowing the existing user’s password. This functionality was removed from the User Interface in ePO 10 and the API has now been disabled. Other protection is in place to reduce the likelihood of this being successful through sending a link to a logged in user.
   NIST CVE-2022-0862
   MITRE CVE-2022-0862

Remediation
To remediate this issue, customers using ePO 5.10 should update to ePO 5.10.0 Update 13.

Go to the Product Downloads site, and download the applicable product update file:

Product

Version

Type

Release Date

ePO

5.10.0 CU 13

Update

March 22, 2022

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
McAfee Enterprise credits SCRT Research Lab for responsibly reporting these flaws:
CVE-2022-0842, CVE-2022-0857, CVE-2022-0858, CVE-2022-0859, CVE-2022-0861, CVE-2022-0862
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?

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 hotfix is installed for ePO.
• Create a query in ePO for the product version of the product installed within your organization.

What is CVSS?
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, McAfee Enterprise has 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?

1. CVE-2022-0842: ePO blind SQL Injection vulnerability

**Base Score**

**5.4**

Attack Vector (AV)

Network (N)

Attack Complexity (AC)

High (H)

Privileges Required (PR)

High (H)

User Interaction (UI)

Required (R)

Scope (S)

Changed (C)

Confidentiality (C)

High (H)

Integrity (I)

None (N)

Availability (A)

None (N)

**Temporal Score (Overall)**

**4.9**

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.  

2. CVE-2022-0857: ePO Reflected Cross-site scripting vulnerability

**Base Score**

**5.4**

Attack Vector (AV)

Network (N)

Attack Complexity (AC)

Low (L)

Privileges Required (PR)

None (N)

User Interaction (UI)

Required (R)

Scope (S)

Unchanged (U)

Confidentiality (C)

Low (L)

Integrity (I)

Low (L)

Availability (A)

None (N)

**Temporal Score (Overall)**

**4.9**

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.  

3. CVE-2022-0858: Cross-site scripting vulnerability in ePO

**Base Score**

**4.3**

Attack Vector (AV)

Network (N)

Attack Complexity (AC)

Low (L)

Privileges Required (PR)

None (N)

User Interaction (UI)

Required (R)

Scope (S)

Unchanged (U)

Confidentiality (C)

None (N)

Integrity (I)

Low (L)

Availability (A)

None (N)

**Temporal Score (Overall)**

**3.9**

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.  

4. CVE-2022-0859: ePO database restoration vulnerability

**Base Score**

**6.5**

Attack Vector (AV)

Local (L)

Attack Complexity (AC)

Low (L)

Privileges Required (PR)

High (H)

User Interaction (UI)

Required (R)

Scope (S)

Unchanged (U)

Confidentiality (C)

High (H)

Integrity (I)

High (H)

Availability (A)

High (H)

**Temporal Score (Overall)**

**5.9**

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.  

5. CVE-2022-0861: ePO XML extended entity 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:** This CVSS version 3.1 vector was used to generate this score.  

6. CVE-2022-0862: ePO password change vulnerability

**Base Score**

**3.1**

Attack Vector (AV)

Network (N)

Attack Complexity (AC)

High (H)

Privileges Required (PR)

Low (L)

User Interaction (UI)

None (N)

Scope (S)

Unchanged (U)

Confidentiality (C)

None (N)

Integrity (I)

Low (L)

Availability (A)

None (N)

**Temporal Score (Overall)**

**2.8**

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.  

7. CVE-2021-42340: ePO and Tomcat

**Base Score**

**5.3**

Attack Vector (AV)

Network (N)

Attack Complexity (AC)

High (H)

Privileges Required (PR)

None (N)

User Interaction (UI)

Required (R)

Scope (S)

Unchanged (U)

Confidentiality (C)

None (N)

Integrity (I)

None (N)

Availability (A)

High (H)

**Temporal Score (Overall)**

**4.8**

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.

Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our external PSIRT website. To see Security Bulletins for McAfee Enterprise products on this website, click Enterprise Security Bulletins. 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 McAfee Enterprise?
If you have information about a security issue or vulnerability with a McAfee Enterprise product, go to the PSIRT website, click Report a Security Vulnerability, and follow the instructions.

How does McAfee Enterprise 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 McAfee Enterprise 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.

McAfee Enterprise only publishes 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.

View our PSIRT policy on the PSIRT website by clicking About PSIRT.
Resources

• 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. McAfee Enterprise disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee Enterprise or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if McAfee Enterprise or its 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 remains at our sole discretion and may be changed or canceled at any time.