Product:	CVE ID:	Impact of Vulnerabilities:	Severity Ratings:	CVSS v3.1 Base/Temporal Scores:
ePolicy Orchestrator (ePO)	CVE-2020-7317	Improper Neutralization of Input (CWE-79)	Medium	4.6 / 4.2
	CVE-2020-7318	Improper Neutralization of Input (CWE-79)	Medium	4.6 / 4.2
	CVE-2020-13935	Denial of Service (CWE-730)	High	7.5
	CVE-2020-9484	Improper Control of Generation of Code (CWE-94)	High	7.0
	CVE-2020-14621	Incorrect Authorization (CWE-863)	Medium	5.3
	CVE-2020-14573	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-14578	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-14579	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-14581	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-2754	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-2755	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-2756	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-2757	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-2764	Improper Input Validation (CWE-20)	Low	3.7
	CVE-2020-2773	Improper Input Validation (CWE-20)	Low	3.7
Highest rating:	High
Impacted versions:	ePO 5.9.x, ePO 5.10.0 earlier than ePO 5.10.0 Update 9 NOTE: CVE-2020-7318 does not impact ePO 5.9.x.
Recommendations:	Install or update to ePO 5.10.0 Update 9
Security Bulletin Replacement:	None
Location of updated software:	Product Downloads site

Article contents:

• Vulnerability Description
• Remediation
• Acknowledgments
• Frequently Asked Questions (FAQs)
• Resources
• Disclaimer

Vulnerability Description
This Security Bulletin contains details of vulnerabilities discovered in the ePO code base and in third-party libraries. They range in severity from Low to High and we recommend you update to the latest ePO version.

Third-party libraries:

Tomcat

1. CVE-2020-13935
   The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service.
    
2. CVE-2020-9484
   When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.

Java

3. CVE-2020-14573
   The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Java SE accessible data.
   
   NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.
    
4. CVE-2020-14578
   Vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
   
   NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.
    
5. CVE-2020-14581
   The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE, Java SE Embedded accessible data.
   
   NOTE: Applies to client and server deployment of Java.
    
6. CVE-2020-14621
   The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Java SE, Java SE Embedded accessible data.
    
7. CVE-2020-14579
   The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
    
8. CVE-2020-2754
   The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
   
   NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.
    
9. CVE-2020-2755
   The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
   
   NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.
    
10. CVE-2020-2756
    The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
    
    NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.
     
11. CVE-2020-2757
    The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
    
    NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.
     
12. CVE-2020-2764
    The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE accessible data.
     
13. CVE-2020-2773
    The vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
    
    NOTE: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets.

ePO code base
These issues only affect the on-premises version of ePO.

14. CVE-2020-7317
    Cross-Site Scripting vulnerability in ePolicy Orchestrator (ePO) prior to 5.10.9 Update 9 allows administrators to inject arbitrary web script or HTML via parameter values for "syncPointList" not being correctly sanitized.
     
15. CVE-2020-7318
    Cross-Site Scripting vulnerability in ePolicy Orchestrator (ePO) prior to 5.10.9 Update 9 allows administrators to inject arbitrary web script or HTML via multiple parameters where the administrator's entries were not correctly sanitized.

Remediation
To remediate this issue:

• Customers using ePO 5.10: Update to ePO 5.10.0 Update 9.
• Customers using ePO 5.9.1 and earlier: Do either of the following:
  • Upgrade to ePO 5.10.0 Update 9 to receive fixes for the Java, Tomcat, and XSS issues.
  • Upgrade to ePO 5.9.1 (if not on it already) and apply ePO 5.9.1 Hotfix EPO-919400 to receive fixes for only the Java and Tomcat issues.
    
    NOTE: ePO 5.9.1 Hotfix EPO-919400 does not address the XSS issue applicable to ePO 5.9.1 (CVE-2020-7317). To remediate this low risk issue, upgrade to ePO 5.10 Update 9.

Go to the Product Downloads site, and download the applicable product update/hotfix files:
 

Product	Version	Type	Release Date
ePO	5.10.0 Update 9	Update	October 13, 2020
ePO	5.9.1 EPO-919400	Hotfix	November 10, 2020

 
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 Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.

Acknowledgments
CWE-2020-7317: We acknowledge Frank Plattel from Radically Open Security for responsibly disclosing this issue.
CWE-2020-7318: We acknowledge Mikhail Klyuchnikov from Positive Technologies for responsibly disclosing this issue.

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 information about how to check the version, see KB52634.
• Create a query in ePO for the product version of the product installed within your organization.

What is CVSS?
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.
 
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?

14. CVE-2020-7317: ePO Cross-Site Scripting vulnerability
     

    Base Score	4.6
    Attack Vector (AV)	Adjacent Network (A)
    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.2
    Exploitability (E)	Proof of concept code (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:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C&version=3.1
     
15. CVE-2020-7318: ePO Cross-Site Scripting vulnerability
     

    Base Score	4.6
    Attack Vector (AV)	Adjacent Network (A)
    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.2
    Exploitability (E)	Proof of concept code (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:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C&version=3.1

Where can I find a list of all Security Bulletins?
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

• 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.