Loading...

Knowledge Center


McAfee Security Bulletin - ePolicy Orchestrator update fixes multiple Apache vulnerabilities (CVE-2017-3169, CVE-2017-7668, and CVE-2017-7679)
Security Bulletins ID:   SB10206
Last Modified:  6/6/2019
Rated:


Summary

First Published: 7/27/2017
 
 Impact of Vulnerability:  Information Disclosure, Denial of Service
 CVE Numbers:  CVE-2017-3169
 CVE-2017-7668
 CVE-2017-7679
 Severity Rating:  Medium / Low
 CVSS v3 Base / Temporal Scores:  CVE-2017-3169: 3.7 / 3.2
 CVE-2017-7668: 6.5 / 5.7
 CVE-2017-7679: 3.7 / 3.2
 Recommendations:  Apply the standalone ePolicy Orchestrator (ePO) Hotfix 1202868 to mitigate this vulnerability
 Security Bulletin Replacement:  None
 Affected Software:  ePO 5.1.3 and earlier
 ePO 5.3.2 and earlier
 ePO 5.9.0 and earlier
 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 was using Apache 2.4.25, which is vulnerable to the following issues:

CVE-2017-3169: mod_ssl Null Pointer Dereference
In Apache httpd 2.2.x before 2.2.33 and 2.4.x before 2.4.26, mod_ssl may dereference a NULL pointer when third-party modules call ap_hook_process_connection() during an HTTP request to an HTTPS port.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3169

CVE-2017-7668: ap_find_token() Buffer Overread
The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows ap_find_token() to search past the end of its input string. By maliciously crafting a sequence of request headers, an attacker may be able to cause a segmentation fault, or to force ap_find_token() to return an incorrect value.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7668

CVE-2017-7679: mod_mime Buffer Overread
In Apache httpd 2.2.x before 2.2.33 and 2.4.x before 2.4.26, mod_mime can read one byte past the end of a buffer when sending a malicious Content-Type response header.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7679

Affected Component:
  • Agent Handler

Remediation

To remediate these issues:
  • ePO 5.1.3: Apply Hotfix EPO513HF1202868.zip.
  • ePO 5.3.2: Apply Hotfix EPO532HF1202868.zip.
  • ePO 5.3.1: Apply Hotfix EPO531HF1202868.zip.
  • ePO 5.9.0: Apply Hotfix EPO590HF1202868.zip.
  • ePO 5.1.0, 5.1.1, or 5.1.2: Upgrade to ePO 5.1.3, 5.3.1, or 5.3.2 and then apply the applicable hotfix.
  • ePO 5.3.0: Upgrade to ePO 5.3.1 or 5.3.2 and then apply the applicable hotfix.
Go to the Product Downloads site and download the applicable product hotfix files:
 
Product Type File Name Release Date
ePO 5.1.3 Hotfix EPO513HF1202868.zip July 27, 2017
ePO 5.3.1 Hotfix EPO531HF1202868.zip July 27, 2017
ePO 5.3.2 Hotfix EPO532HF1202868.zip July 27, 2017
ePO 5.9.0 Hotfix EPO590HF1202868.zip July 27, 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. McAfee strongly recommends installing the provided hotfix specified in the Remediation table.

Mitigations

None. McAfee strongly recommends installing the provided 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?

NOTE: The CVSS scores below are different than the original CVE scores. The below scores were determined based on ePO usage of the vulnerable component.
 
CVE-2017-3169
 
 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.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://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L/E:U/RL:O/RC:C

CVE-2017-7668

 
 Base Score 6.5
 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) High (H)
 Temporal Score (Overall) 5.7
 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://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H/E:U/RL:O/RC:C

CVE-2017-7679
 
 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.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://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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 cancelled at any time.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

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.