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: 5/4/2022
Last Modified: 5/4/2022
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: | Product Downloads site |
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 and download the applicable product hotfix files:
Go to the Product Downloads site 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 InstructionsFor instructions to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Frequently Asked Questions (FAQs)
How do I know whether my product is vulnerable?
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, we've 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, we've 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?
All Security Bulletins are published on our Knowledge Center. 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 you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our 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.
We only publish 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.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.
- 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 fields to have your password and instructions emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't 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 shouldn't 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 aren't 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 remain at our sole discretion and may be changed or canceled at any time.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't 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 aren't 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 remain at our sole discretion and may be changed or canceled at any time.
