Loading...

Knowledge Center


McAfee Security Bulletin - ePolicy Orchestrator update fixes multiple Java vulnerabilities (CVE-2017-10356, CVE-2016-10165, CVE-2017-10355, CVE-2017-10281, CVE-2017-10295, and CVE-2017-10345)
Security Bulletins ID:   SB10212
Last Modified:  1/26/2018

Summary

First Published: 12/18/2017
 
 Impact of Vulnerability:  Unauthorized Access
 Information Leak / Disclosure (CWE-717, OWASP 2004:A6)
 Denial of Service (CWE-730, OWASP 2004:A9)
 CVE Numbers:  CVE-2017-10356
 CVE-2016-10165
 CVE-2017-10355
 CVE-2017-10281
 CVE-2017-10295
 CVE-2017-10345
 Severity Rating:  Medium, Low
 CVSS v3 Base and Temporal Scores:  CVE-2017-10356: 6.2/5.4
 CVE-2016-10165: 5.3/4.6
 CVE-2017-10355: 5.3/4.6
 CVE-2017-10281: 5.3/4.6
 CVE-2017-10295: 4.0/3.5
 CVE-2017-10345: 3.1/2.7
 Recommendations:  Upgrade to ePolicy Orchestrator (ePO) 5.9.1 or apply ePO 5.3.3 hotfix EPO533HF1221099
 Security Bulletin Replacement:  None
 Affected Software:
  •  ePO 5.1.3, 5.1.2, 5.1.1, and 5.1.0
  •  ePO 5.3.3, 5.3.2, and 5.3.1
  •  ePO 5.9.0
 Location of Updated Software:  http://www.mcafee.com/us/downloads/downloads.aspx

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:

Description

ePO is vulnerable to the Java CVEs mentioned above.
 
This ePO update resolves the following issues:
  • CVE-2017-10356
    Easily exploitable 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.
    Subcomponent: Security
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10356
     
  • CVE-2016-10165
    The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2) allows remote attackers to obtain sensitive information or cause a denial of service via an image with a crafted ICC profile, which triggers an out-of-bounds heap read.
    Subcomponent: 2D
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10165
     
  • CVE-2017-10355
    Easily exploitable 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.
    Subcomponent: Networking
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10355
     
  • CVE-2017-10281
    Easily exploitable 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.
    Subcomponent: Serialization
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10281
     
  • CVE-2017-10295
    Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Java SE. While the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert, or delete access to some of Java SE accessible data.
    Subcomponent: Networking
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10295
     
  • CVE-2017-10345
    Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE.
    Subcomponent: Networking
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10345
Affected Component:
ePO Java core web services

Remediation

To remediate this issue:
  • Users of ePO 5.1.3 or earlier should upgrade to ePO 5.3.3 and apply hotfix EPO533HF1221099 or upgrade to ePO 5.9.1.
  • Users of ePO 5.3.2 or earlier should upgrade to ePO 5.3.3 and apply hotfix EPO533HF1221099 or upgrade to ePO 5.9.1.
  • Users of ePO 5.3.3 should apply hotfix EPO533HF1221099 or upgrade to ePO 5.9.1.
  • Users of ePO 5.9.0 should upgrade to ePO 5.9.1.
NOTE: All FIPS 140-2 installed customers running ePO 4.6.4 can upgrade to ePO 5.1.x for maintaining FIPS compliant installations.

Go to the Product Downloads site and download the applicable product patch/hotfix files:
 
Product Type File Name Release Date
ePO 5.9.1 Patch EPO591L.zip November 30, 2017
ePO 5.3.3 Hotfix EPO533HF1221099.zip December 20, 2017

Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, security updates, patches, and hotfixes. Review the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions on how to install these updates.

Product Specific Notes

ePO 5.1.x reached End of Life on December 31, 2017. McAfee highly recommends that all customers upgrade to ePO 5.3.x or 5.9.x.

Workaround

None. McAfee strongly recommends installing the latest ePO patch or the hotfix specified in the Remediation table.

Acknowledgements

None.

Frequently Asked Questions (FAQs)

How do I know whether my McAfee product is vulnerable or not?
For ePO:
Check the version and build of ePO that is installed. For information on 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, please visit the CVSS website at: http://www.first.org/cvss/.

When calculating CVSS scores, McAfee 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 do not factor into a score any potential follow-on exploits that might be made possible by successful exploitation of the issue being scored
 
What are the CVSS scoring metrics that have been used?
 
CVE-2017-10356: ePO and Java
 
 Base Score 6.2
 Attack Vector (AV) Local (L)
 Attack Complexity (AC) Low (L)
 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) 5.4
 Exploitability (E) Unproven that Exploit Exists (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C


CVE-2016-10165: 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) Low (N)
 Integrity (I) None (N)
 Availability (A) None (N)
 Temporal Score (Overall) 4.6
 Exploitability (E) Unproven that Exploit Exists (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 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:N/A:N/E:U/RL:O/RC:C

CVE-2017-10355: 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) 4.6
 Exploitability (E) Unproven (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 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:U/RL:O/RC:C

CVE-2017-10281: 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) 4.6
 Exploitability (E) Unproven that Exploit Exists (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 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:U/RL:O/RC:C

CVE-2017-10295: ePO and Java 
 
 Base Score 4.0
 Attack Vector (AV) Network (N)
 Attack Complexity (AC) High (H)
 Privileges Required (PR) None (N)
 User Interaction (UI) None (N)
 Scope (S) Changed (C)
 Confidentiality (C) None (N)
 Integrity (I) Low (L)
 Availability (A) None (N)
 Temporal Score (Overall) 3.5
 Exploitability (E) Unproven that Exploit Exists (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 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:C/C:N/I:L/A:N/E:U/RL:O/RC:C

CVE-2017-10345: 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) None (N)
 Integrity (I) None (N)
 Availability (A) Low (L)
 Temporal Score (Overall) 2.7
 Exploitability (E) Unproven that Exploit Exists (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 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:N/I:N/A:L/E:U/RL:O/RC:C

Where can I find a list of all security bulletins or how do I report a product vulnerability?
To find a list of all security bulletins, or if you have information about a security issue or vulnerability with a McAfee product, please visit our product security website at: http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx.

Resources

To contact Technical Support, log on to the ServicePortal and go to the Create a Service Request page at https://support.mcafee.com/ServicePortal/faces/serviceRequests/createSR:
  • 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 required fields. Your password and logon instructions will be emailed to you.

Disclaimer

The information provided in this security bulletin is provided as is without warranty of any kind. McAfee disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if McAfee or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
 
Any future product release dates mentioned in this security bulletin are intended to outline our general product direction and they should not 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 are not 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.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.