Security Bulletin - ePolicy Orchestrator update fixes Java vulnerabilities (CVE-2019-2745, CVE-2019-2762, CVE-2019-2766, CVE-2019-2769, CVE-2019-2816, and CVE-2019-2842)
Security Bulletins ID:
SB10300
Last Modified: 2022-05-04 16:47:01 Etc/GMT
Last Modified: 2022-05-04 16:47:01 Etc/GMT
Summary
First Published: November 12, 2019
Article contents: Vulnerability Description
We strongly recommend that you install the latest update or hotfix for your version of ePO.
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.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For ePO:
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about how to check the version, see: KB52634.
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?
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.
| Impact of Vulnerability: | Denial of Service (CWE-730, OWASP 2004:A9) Improper Access Control (CWE-287) |
| CVE ID: | CVE-2019-2745 CVE-2019-2762 CVE-2019-2766 CVE-2019-2769 CVE-2019-2816 CVE-2019-2842 |
| Severity Rating: | Medium |
| CVSS v3 Base/Temporal Scores: | CVE-2019-2745: 5.1/4.9 CVE-2019-2762: 5.3/5.1 CVE-2019-2766: 3.1/3.0 CVE-2019-2769: 5.3/5.1 CVE-2019-2816: 4.8/4.6 CVE-2019-2842: 3.7/3.6 |
| Recommendations: | Install or update to one of the following ePO versions:
|
| Security Bulletin Replacement: | None |
| Affected Software: | • ePO 5.10.0 prior to Update 5 • ePO 5.9.0 and 5.9.1 |
| 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
- CVE-2019-2745
Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Java SE executes to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java SE accessible data.
https://nvd.nist.gov/vuln/detail/CVE-2019-2745
- CVE-2019-2762
Easily exploitable 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.
https://nvd.nist.gov/vuln/detail/CVE-2019-2762
- CVE-2019-2766
Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE, Java SE Embedded accessible data.
https://nvd.nist.gov/vuln/detail/CVE-2019-2766
- CVE-2019-2769
Easily exploitable 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.
https://nvd.nist.gov/vuln/detail/CVE-2019-2769
- CVE-2019-2816
Difficult to exploit 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 as well as unauthorized read access to a subset of Java SE, Java SE Embedded accessible data.
https://nvd.nist.gov/vuln/detail/CVE-2019-2816
- CVE-2019-2842
Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE.
https://nvd.nist.gov/vuln/detail/CVE-2019-2842
We strongly recommend that you install the latest update or hotfix for your version of ePO.
- Users of ePO 5.10 should update to ePO 5.10 Update 5.
- Users of ePO 5.9.1 should apply Hotfix EPO-87800_591, or upgrade to ePO 5.10 Update 5.
- Users of ePO 5.9.0 should upgrade to ePO 5.9.1 and apply Hotfix EPO-87800_591, or upgrade to ePO 5.10 Update 5.
| Product | Version | Type | File Name | Release Date |
| ePO | 5.10 | Update | ePO 5.10.0 Update 5 | November 12, 2019 |
| ePO | 5.9.1 | Hotfix | EPO-87800_591.zip | November 12, 2019 |
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.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For ePO:
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about how to check the version, see: KB52634.
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?
- CVE-2019-2745: ePO and Java
Base Score 5.1 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) None (N) User Interaction (UI) None (N) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) None (N) Availability (A) None (N) Temporal Score (Overall) 4.9 Exploitability (E) Not Defined (X) 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:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:X/RL:O/RC:C&version=3.1
- CVE-2019-2762: ePO and Java
Base Score 5.3 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) None (N) Integrity (I) None (N) Availability (A) Low (L) Temporal Score (Overall) 5.1 Exploitability (E) Not Defined (X) 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:N/I:N/A:L/E:X/RL:O/RC:C&version=3.1
- CVE-2019-2766: ePO and Java
Base Score 3.1 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) Low (L) Integrity (I) None (N) Availability (A) None (N) Temporal Score (Overall) 3.0 Exploitability (E) Not Defined (X) 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:H/PR:N/UI:R/S:U/C:L/I:N/A:N/E:X/RL:O/RC:C&version=3.1
- CVE-2019-2769: ePO and Java
Base Score 5.3 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) None (N) Integrity (I) None (N) Availability (A) Low (L) Temporal Score (Overall) 5.1 Exploitability (E) Not Defined (X) 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:N/I:N/A:L/E:X/RL:O/RC:C&version=3.1
- CVE-2019-2816: ePO and Java
Base Score 4.8 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) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 4.6 Exploitability (E) Not Defined (X) 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:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:X/RL:O/RC:C&version=3.1
- CVE-2019-2842: ePO and Java
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.6 Exploitability (E) Not Defined (X) 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:H/PR:N/UI:N/S:U/C:N/I:N/A:L/E:X/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.
