Security Bulletin: VirusScan Enterprise update fixes protections bypass vulnerability (CVE-2016-4534)
Security Bulletins ID:
SB10158
Last Modified: 5/4/2022
Last Modified: 5/4/2022
Summary
First Published: 4/29/2016
| Impact of Vulnerability: | Application Protections Bypass (CWE-592) |
| CVE Numbers: | CVE-2016-4534 |
| Severity Rating: | Low |
| CVSS v3 Base / Temporal Scores: | 2.9 / 2.8 |
| Recommendations: | Install all patches described in SB10151 first, then install the VirusScan Enterprise (VSE) hotfix. |
| Security Bulletin Replacement: | Related to SB10151: same discoverer, similar patch sequence, different vulnerability. |
| Affected Software: | VSE 8.8.0 |
| 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 addresses an issue with VSE where closing the registry handles for the VSE process mcconsole.exe using Process Explorer (or similar tools) could be exploited to unlock the password protected VirusScan Console window.
This trusted access bypass vulnerability allows access to resources normally protected by VSE.
CVE-2016-4534
The McAfee VirusScan Console (mcconsol.exe) in McAfee VirusScan Enterprise 8.8.0 before Hotfix 1123565 (8.8.0.1546) on Windows allows local administrators to bypass intended self-protection rules and unlock the console window by closing registry handles.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4534
CVE-2016-4534
The McAfee VirusScan Console (mcconsol.exe) in McAfee VirusScan Enterprise 8.8.0 before Hotfix 1123565 (8.8.0.1546) on Windows allows local administrators to bypass intended self-protection rules and unlock the console window by closing registry handles.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4534
CWE-592
Application Protections Bypass
Application Protections Bypass
Remediation
IMPORTANT: Install all patches described in SB10151 first, then apply this VSE hotfix. This hotfix supports both VSE 8.8.0 Patch 6 and VSE 8.8.0 Patch 7.
| Product | Type | Version | Release Build | File Name | Release Date |
| VSE | Hotfix | 8.8.0 Patch 6/7 Hotfix 1123565 | 8.8.0.1546 | VSE880P7HF1123565.zip | April 29, 2016 |
Recommended Installation Sequence
Install all patches described in SB10151 first, then apply the VSE hotfix. For example, first install: VSE 8.8.0.1528, and then install: VSE 8.8.0 Patch 6/7 Hotfix 1123565 8.8.0.1546 (above).
For 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.
Acknowledgements
We credit Maurizio Agazzini (also known as inode) https://www.linkedin.com/in/maurizio-agazzini-b915243 from Mediaservice.net (http://techblog.mediaservice.net/author/inode/) for reporting this flaw in VSE.
He reported it as one of two examples of the same vulnerability; however, upon further investigation it was determined that two different vulnerabilities were actually reported. This hotfix fixes Example #1 described at https://packetstormsecurity.com/files/136089. SB10151 fixes Example #2 described at https://packetstormsecurity.com/files/136089.
He reported it as one of two examples of the same vulnerability; however, upon further investigation it was determined that two different vulnerabilities were actually reported. This hotfix fixes Example #1 described at https://packetstormsecurity.com/files/136089. SB10151 fixes Example #2 described at https://packetstormsecurity.com/files/136089.
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:
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-2016-4534: Unlocking the password protected VirusScan Console window by closing the registry handles for the VSE process "mcconsole.exe"
CVSS v3.0 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:H/UI:R/S:U/C:N/I:L/A:L/E:F/RL:T/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.
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.
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
| Base Score | 2.9 |
| Attack Vector (AV) | Local (L) |
| Attack Complexity (AC) | High (H) |
| Privileges Required (PR) | High (H) |
| User Interaction (UI) | Required (R) |
| Scope (S) | Unchanged (U) |
| Confidentiality (C) | None (N) |
| Integrity (I) | Low (L) |
| Availability (A) | Low (L) |
| Temporal Score (Overall) | 2.8 |
| Exploitability (E) | Functional (F) |
| Remediation Level (RL) | Temporary Fix (T) |
| 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:H/UI:R/S:U/C:N/I:L/A:L/E:F/RL:T/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.
