Loading...

Knowledge Center


McAfee Security Bulletin - ePolicy Orchestrator update fixes two Java vulnerabilities (CVE-2018-2942 and CVE-2018-2952)
Security Bulletins ID:   SB10247
Last Modified:  8/14/2018
Rated:


Summary

First Published: August 14, 2018
 
 Impact of Vulnerability: Unauthorized Access
 CVE ID: CVE-2018-2942
CVE-2018-2952
 Severity Rating: CVE-2018-2942: High
CVE-2018-2952: Low
 CVSS v3 Base/Temporal Scores: CVE-2018-2942: 8.3 / 7.9
CVE-2018-2952: 3.7 / 3.6
 Recommendations: Apply EPO5xHF1248224 or upgrade to ePolicy Orchestrator (ePO) 5.10
 Security Bulletin Replacement: None
 Affected Software: ePO 5.3.3, 5.3.2, 5.3.1, and 5.3.0
ePO 5.9.1 and 5.9.0
 Location of updated software: http://www.mcafee.com/us/downloads/downloads.aspx
 
To receive email notification when this Security Bulletin is updated, click Subscribe on the right side of the page. You must be logged in to subscribe.
 
Article contents: Vulnerability Description
This update resolves the following vulnerabilities:
  1. CVE-2018-2942
    Difficult to exploit vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Java SE. 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.
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2942
     
  2. CVE-2018-2952
    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 unauthorized ability to cause a partial denial of service (partial DOS) of Java SE.
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2952
Affected Component:
  • ePO Java core web services
Remediation
To remediate these issues:
  • Users of ePO 5.3.2 or earlier are recommended to upgrade to ePO 5.3.3 or 5.9.1 and apply EPO5xHF1248224. Alternatively, you may upgrade to ePO 5.10.
  • Users of ePO 5.3.3 are recommended to apply EPO5xHF1248224 or upgrade to ePO 5.10.
  • Users of ePO 5.9.0 are recommended to upgrade to ePO 5.9.1 and apply EPO5xHF1248224. Alternatively, you may upgrade to ePO 5.10.
  • Users of ePO 5.9.1 are recommended to apply EPO5xHF1248224 or upgrade to ePO 5.10.
Go to the Product Downloads site, and download the applicable product update files:
 
Product Type File Name Release Date
ePO 5.9.1 Hotfix EPO5xHF1248224.zip* August 14, 2018
ePO 5.3.3 Hotfix  EPO5xHF1248224.zip*  August 14, 2018

*Alternatively you may upgrade to ePO 5.10, which also corrects these issues. 

Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, updates, 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 (EOL) on December 31, 2017. McAfee highly recommends that all customers upgrade to ePO 5.9.x or 5.10.x.
Workaround
None. McAfee strongly encourages installing the ePO hotfix specified in the Remediation table.
Acknowledgments
None.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable or not?
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 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 the successful exploitation of the issue being scored.
 
What are the CVSS scoring metrics?
  1. CVE-2018-2942: ePO and Java
     
    Base Score 8.3
    Attack Vector (AV) Network (N)
    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) 7.9
    Exploitability (E) Not Defined (X)
    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:C/C:H/I:H/A:H/E:X/RL:O/RC:C
     
  2. CVE-2018-2952: 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.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:L/E:X/RL:O/RC:C
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our external PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Security Bulletins. 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 McAfee?
If you have information about a security issue or vulnerability with a McAfee product, visit the McAfee PSIRT website for instructions at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Report a Security Vulnerability.
 
How does McAfee respond to this and any other reported security flaws?
McAfee's key priority is the security of our customers. If a vulnerability is found within any of McAfee's 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.
 
McAfee only publishes 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.
 
View our PSIRT policy on the McAfee PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > About PSIRT.
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 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 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

Languages:

This article is available in the following languages:

English United States
Japanese

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.