Security Bulletin - ePolicy Orchestrator update addresses two product vulnerabilities (CVE-2021-31834 and CVE-2021-31835) and updates Java, OpenSSL, and Tomcat
Security Bulletins ID:
SB10366
Last Modified: 2022-05-04 19:28:58 Etc/GMT
Last Modified: 2022-05-04 19:28:58 Etc/GMT
Summary
First Published: October 21, 2021
Article contents:
This release addresses two Cross-Site Scripting (XSS) vulnerabilities in the ePO administrator User Interface, and updates three libraries that ePO uses. Both issues require administrator access.
The third-party libraries updated in this release, along with details on CVEs that impacted ePO, are below.
To remediate this issue, customers using ePO 5.10 should update to ePO 5.10 Update 11.
Go to the Product Downloads site, and download the applicable product update file:
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.
Acknowledgments
We credit the following researcher for responsibly reporting the flaws:
CVE-2021-31835 - Michal Skowron from ING Tech Poland
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:
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 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 CU 11 | CVE-2021-31834 | CWE 79: Cross-Site Scripting (XSS) | Medium | 4.8 / 4.3 |
| CVE-2021-31835 | CWE 79: Cross-Site Scripting (XSS) | Medium | 4.8 / 4.3 | ||
| Java CVE-2021-2161 | NVD-CWE-noinfo: Insufficient Information | Medium | 5.9 | ||
| Java CVE-2021-2432 | NVD-CWE-noinfo: Insufficient Information | Low | 3.7 | ||
| OpenSSL CVE-2021-3712 OpenSSL CVE-2021-23840 |
CWE 125: Out-of-bounds Read CWE 190: Integer overflow or Wraparound |
High Low |
7.4 3.7 |
||
| Tomcat CVE-2021-30639 Tomcat CVE-2021-33037 |
CWE 755: Improper Handling of Exceptional Conditions CWE 444: Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') |
High Medium |
7.5 5.3 |
||
| Recommendations: | Install or update to ePO 5.10 CU 11 | ||||
| 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 release addresses two Cross-Site Scripting (XSS) vulnerabilities in the ePO administrator User Interface, and updates three libraries that ePO uses. Both issues require administrator access.
The third-party libraries updated in this release, along with details on CVEs that impacted ePO, are below.
- Java has been updated to the July 2021 update.
- CVE-2021-2161 from the April 2021 update rated as Medium (CVSS 5.9)
Oracle Critical Patch Update Advisory - CVE-2021-2432 from the July 2021 update rated as Low (CVSS 3.7)
Oracle Critical Patch Update Advisory
- CVE-2021-2161 from the April 2021 update rated as Medium (CVSS 5.9)
- OpenSSL has been updated to 1.0.2za from 1.0.2t. For details of the issues that OpenSSL addressed, see the OpenSSL vulnerabilities page.
- Tomcat has been updated to 9.0.52 from 9.0.41. For details of the issues that Tomcat addressed, see the Tomcat vulnerabilities page.
- CVE-2021-31834
Stored Cross-Site Scripting vulnerability in ePolicy Orchestrator (ePO) prior to 5.10 Update 11 allows ePO administrators to inject arbitrary web script or HTML via multiple parameters where the administrator's entries were not correctly sanitized.
NVD CVE-2021-31834
MITRE CVE-2021-31834
- CVE-2021-31835
Cross-Site Scripting vulnerability in ePolicy Orchestrator (ePO) prior to 5.10 Update 11 allows ePO administrators to inject arbitrary web script or HTML via a specific parameter 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 that they can pass parameters to, triggering the Cross-Site Scripting vulnerability.
- Add a new registered command to the ePO system that 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 another ePO user. Execution of these commands is not granted by default to non-administrator ePO users.
MITRE CVE-2021-31835
To remediate this issue, customers using ePO 5.10 should update to ePO 5.10 Update 11.
Go to the Product Downloads site, and download the applicable product update file:
| Product | Version | Type | Release Date |
| ePO | 5.10 Update 11 | Update | October 21, 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.
Acknowledgments
We credit the following researcher for responsibly reporting the flaws:
CVE-2021-31835 - Michal Skowron from ING Tech Poland
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.
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 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-31834: ePO Cross-Site Scripting vulnerability
Base Score 4.8 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) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 4.3 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-31835: ePO Cross-Site Scripting vulnerability
Base Score 4.8 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) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 4.3 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-23840: ePO and OpenSSL
(Adjusted score based on ePO usage of OpenSSL)Base Score 3.7 Attack Vector (AV) Network (N) Attack Complexity (AC) High (H) Privileges Required (PR) None (N) User Interaction (UI) None (N) Scope (S) Unchanged (U) Confidentiality (C) None (N) Integrity (I) None (N) Availability (A) Low (L) Temporal Score (Overall) 3.4 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.
