Loading...

Knowledge Center


McAfee Security Bulletin - ePolicy Orchestrator update fixes multiple Oracle Java vulnerabilities (CVE-2017-3511, CVE-2017-3526, CVE-2017-3533, and CVE-2017-3544)
Security Bulletins ID:   SB10200
Last Modified:  6/6/2019
Rated:


Summary

First Published: May 25, 2017
 
 Impact of Vulnerability:  Denial of Service (CWE-730, OWASP 2004:A9), Unauthorized Access
 CVE Numbers:  CVE-2017-3511
 CVE-2017-3526
 CVE-2017-3533
 CVE-2017-3544
 Severity Rating:  High
 Base / Overall CVSS v3 Scores:  7.7/6.7
 5.9/5.2
 3.7/3.2
 3.7/3.2
 Recommendations:  Apply the standalone hotfix specified in the Remediation table
 Security Bulletin Replacement:  None
 Affected Software:
  • ePolicy Orchestrator (ePO) 5.1.3 and earlier
  • ePO 5.3.2 and earlier
  • 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 following CVEs, which were reported in Oracle's April 2017 Java SE update.
 
Oracle's Critical Patch Updates, Security Alerts, and Third Party Bulletins:
http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html

This ePO update resolves the following issues:
  • CVE-2017-3511:
    This difficult to exploit vulnerability allows an unauthenticated attacker with a logon to the infrastructure where Java SE executes to compromise Java SE. A successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. Subcomponent: JCE
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3511
     
  • CVE-2017-3526:
    This difficult to exploit vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in an unauthorized ability to cause a hang or frequently repeatable crash (complete Denial of Service) of Java SE. Subcomponent: JAXP
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3526
     
  • CVE-2017-3533:
    This difficult to exploit vulnerability allows an unauthenticated attacker with network access via FTP 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. Subcomponent: Networking
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3533
     
  • CVE-2017-3544:
    This difficult to exploit vulnerability allows an unauthenticated attacker with network access via SMTP 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. Subcomponent: Networking
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3544
Affected Component:
  • ePO Java core web services

Remediation

These fixes will be included in the next ePO patch when scheduled. The following hotfixes are available:
  • Users of ePO 5.1.x should upgrade to ePO 5.1.3, 5.3.1, or 5.3.2 and then apply hotfix epo51x53xHF1191750.zip.
  • Users of ePO 5.3.0 should upgrade to ePO 5.3.1 or 5.3.2 and then apply hotfix epo51x53xHF1191750.zip.
  • Users of ePO 5.9.0 should apply hotfix EPO590HF1208662.zip.
NOTE: The Hotfix for ePO 5.9.0 was originally listed as epo590HF1191751.zip. This hotfix has been removed and replaced with EPO590HF1208662.zip. If you installed the original Hotfix, install EPO590HF1208662.zip to remove and replace the previous Hotfix.

Refer to the upgrade instructions in the Hotfix Release Notes for further details.
 
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.1.3 Hotfix epo51x53xHF1191750.zip May 25, 2017
ePO 5.3.1 Hotfix epo51x53xHF1191750.zip May 25, 2017
ePO 5.3.2 Hotfix epo51x53xHF1191750.zip May 25, 2017
ePO 5.9.0 Hotfix EPO590HF1208662.zip Aug 24, 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.

Workaround

None. Installing the provided hotfix specified in the Remediation table is strongly encouraged.

Acknowledgements

This vulnerability was first disclosed by Oracle's pre-patch announcement for the April 2017 quarterly Security Bulletin:
http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html

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-3511: McAfee ePO and Oracle JRE
 
 Base Score 7.7
 Attack Vector (AV) Local (L)
 Attack Complexity (AC) High (H)
 Privileges Required (PR) None (N)
 User Interaction (UI) Required (R)
 Scope (S) Changed (C)
 Confidentiality (C) High (H)
 Integrity (I) High (H)
 Availability (A) High (H)
 Temporal Score (Overall) 6.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:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C


CVE-2017-3526: McAfee ePO and Oracle JRE
 
 Base Score 5.9
 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) High (H)
 Temporal Score (Overall) 5.2
 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:U/C:N/I:N/A:H/E:U/RL:O/RC:C

CVE-2016-3533: McAfee ePO and Oracle JRE 
 
 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) Low (L)
 Availability (A) None (N)
 Temporal Score (Overall) 3.2
 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:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C

CVE-2016-3544: McAfee ePO and Oracle JRE 
 
 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) Low (L)
 Availability (A) None (N)
 Temporal Score (Overall) 3.2
 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:H/PR:N/UI:N/S:U/C:N/I:L/A:N/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 cancelled at any time.

Rate this document

Languages:

This article is available in the following languages:

English United States
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

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