McAfee Security Bulletin: Application Control update fixes system crash caused by certain inputs to Application Control driver API on Windows 32-bit systems
Security Bulletins ID:
SB10145
Last Modified: 4/7/2017
Last Modified: 4/7/2017
Summary
First Published: 12/30/2015
| Impact of Vulnerability: | Denial of Service (CWE-730, OWASP 2004:A9) Input Validation (CWE-20) Privilege Escalation (CWE-274) |
| CVE Numbers: | CVE-2016-1715 |
| Severity Rating: | Medium |
| Base / Overall CVSS v2 Scores: | 6.6/5.9 |
| Base / Overall CVSS v3 Scores: | 5.5/4.3 |
| Recommendations: | Install or update to one of the following McAfee Application Control (MAC) versions:
|
| Security Bulletin Replacement: | None |
| Affected Software: |
|
| 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
This update resolves an issue with the Application Control Driver API on Windows 32-bit systems where sending certain inputs to the driver causes a system crash or privilege escalation.
CVE-2016-1715
The swin.sys kernel driver in McAfee Application Control (MAC) 6.1.0 before build 706, 6.1.1 before build 404, 6.1.2 before build 449, 6.1.3 before build 441, and 6.2.0 before build 505 on 32-bit Windows platforms allows local users to cause a denial of service (memory corruption and system crash) or gain privileges via a 768 syscall, which triggers a zero to be written to an arbitrary kernel memory location.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1715
CVE-2016-1715
The swin.sys kernel driver in McAfee Application Control (MAC) 6.1.0 before build 706, 6.1.1 before build 404, 6.1.2 before build 449, 6.1.3 before build 441, and 6.2.0 before build 505 on 32-bit Windows platforms allows local users to cause a denial of service (memory corruption and system crash) or gain privileges via a 768 syscall, which triggers a zero to be written to an arbitrary kernel memory location.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1715
Remediation
Update to the latest MAC hotfix.
Go to the Product Downloads site (http://www.mcafee.com/us/downloads/downloads.aspx) and download the applicable product hotfix files:
Go to the Product Downloads site (http://www.mcafee.com/us/downloads/downloads.aspx) and download the applicable product hotfix files:
| Product | Release Date |
| MAC 6.1.0 build 706 (or later) | December 24, 2015 |
| MAC 6.1.1 build 404 (or later) | December 24, 2015 |
| MAC 6.1.2 build 449 (or later) | December 24, 2015 |
| MAC 6.1.3 build 441 (or later) | December 22, 2015 |
| MAC 6.2.0 build 505 (or later) | December 22, 2015 |
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.
Frequently Asked Questions (FAQs)
How do I know whether my McAfee product is vulnerable or not?
For Endpoint products:
Use the following instructions for endpoint or client based products:
Check the version and build of ePO that is installed. For information on how to check the version, see KB52634
For Appliances:
Use the following instructions for Appliance based products:
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 v2 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.
CVSS v3 scoring is in final review as of March 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved.
https://www.first.org/cvss/v3/development
https://www.first.org/cvss/calculator/3.0
What are the CVSS scoring metrics that have been used?
CVE-2016-1715
CVSS v3 Scoring:
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:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:H/E:P/RL:O/RC:C
CVSS v2.0 Scoring:
For Endpoint products:
Use the following instructions for endpoint or client based products:
- Right-click on the McAfee tray shield icon on the Windows task bar.
- Select Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. The product version is displayed.
Check the version and build of ePO that is installed. For information on how to check the version, see KB52634
For Appliances:
Use the following instructions for Appliance based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version is displayed.
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 v2 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.
CVSS v3 scoring is in final review as of March 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved.
https://www.first.org/cvss/v3/development
https://www.first.org/cvss/calculator/3.0
CVE-2016-1715
| Base Score | 6.6 |
| Attack Vector (AV) | Local (L) |
| Attack Complexity (AC) | High (H) |
| Privileges Required (PR) | Low (L) |
| User Interaction (UI) | Required (R) |
| Scope (S) | Changed (C) |
| Confidentiality (C) | Low (L) |
| Integrity (I) | Low (L) |
| Availability (A) | High (H) |
| Temporal Score (Overall) | 5.9 |
| Exploitability (E) | Proof-of-Concept (P) |
| 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:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:H/E:P/RL:O/RC:C
CVSS v2.0 Scoring:
| Base Score | 5.5 |
| Related exploit range (AccessVector) | Local (L) |
| Attack complexity (AccessComplexity) | Medium (M) |
| Level of authentication needed (Authentication) | Single (S) |
| Confidentiality impact | Partial (P) |
| Integrity impact | Partial (P) |
| Availability impact | Complete (C) |
| Temporal Score (Overall) | 4.3 |
| Availability of exploit (Exploitability) | Proof of Concept Code (POC) |
| Type of fix available (RemediationLevel) | Official Fix (OF) |
| Level of verification that vulnerability exists (ReportConfidence) | Confirmed (C) |
NOTE: The below CVSS version 2.0 vector was used to generate this score.
https://nvd.nist.gov/cvss.cfm?calculator&version=2&vector=(AV:L/AC:M/Au:S/C:P/I:P/A:C/E:POC/RL:OF/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.
