Security Bulletin: Authentication bypass in Host Intrusion Prevention Services 8.0 allows authenticated users to manipulate the product’s registry keys using specific conditions (CVE-2016-8007)
Security Bulletins ID:
SB10173
Last Modified: 5/4/2022
Last Modified: 5/4/2022
Summary
First Published: 10/19/2016
| Impact of Vulnerability: | Configuration (CWE-16) Denial of Service (CWE-730, OWASP 2004:A9) Permissions, Privileges, and Access Control (CWE-264) |
| CVE Numbers: | CVE-2016-8007 |
| Severity Rating: | Medium |
| Base / Overall CVSS v3 Scores: | 6.0 / 5.4 |
| Recommendations: | Keep Host IPS enabled or update to Host Intrusion Prevention Services 8.0 Patch 8 |
| Security Bulletin Replacement: | None |
| Affected Software: | Host Intrusion Prevention Services 8.0 Patch 7 and earlier |
| 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
CVE-2016-8007
Authentication bypass vulnerability in Host Intrusion Prevention Services (HIPS) 8.0 Patch 7 and earlier allows authenticated users to manipulate the product's registry keys via specific conditions.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8007
CWE-16
An administrator could expose the vulnerability by disabling Host IPS.
http://cwe.mitre.org/data/definitions/16.html
CWE-730
A non-admin user could stop some Host Intrusion Prevention services and modules.
http://cwe.mitre.org/data/definitions/730.html
CWE-264
Host Intrusion Prevention Services 8.0 fails to set its registry keys with sufficient permissions.
http://cwe.mitre.org/data/definitions/264.html
OWASP 2004:A9
A non-admin user could stop some Host Intrusion Prevention services and modules.
https://www.owasp.org/index.php/Top_10_2004
https://www.owasp.org/index.php/A9_2004_Application_Denial_of_Service
This flaw is encountered if an administrator disables Host Intrusion Prevention Services 8.0 Host IPS.
Affected Component:
Authentication bypass vulnerability in Host Intrusion Prevention Services (HIPS) 8.0 Patch 7 and earlier allows authenticated users to manipulate the product's registry keys via specific conditions.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8007
An administrator could expose the vulnerability by disabling Host IPS.
http://cwe.mitre.org/data/definitions/16.html
A non-admin user could stop some Host Intrusion Prevention services and modules.
http://cwe.mitre.org/data/definitions/730.html
Host Intrusion Prevention Services 8.0 fails to set its registry keys with sufficient permissions.
http://cwe.mitre.org/data/definitions/264.html
A non-admin user could stop some Host Intrusion Prevention services and modules.
https://www.owasp.org/index.php/Top_10_2004
https://www.owasp.org/index.php/A9_2004_Application_Denial_of_Service
- All Host Intrusion Prevention Services 8.0 modules
Remediation
| Product | Type | Version | File Name | Release Date |
| Host Intrusion Prevention Services | Patch | 8.0 Patch 8 | HIP_Client 8.0.0 Build 3828 Package #1 (AAA-LICENSED-RELEASE-PATCH 8).Zip MSP_PATCH HIP_Client-WIN 8.0.0 Build 3828 Package #1 (AAA-LICENSED-RELEASE-PATCH 8).Zip |
August 25, 2016 |
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: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?
CVE-2016-8007: Host Intrusion Prevention Services weak registry permissions
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:U/C:N/I:H/A:H/E:P/RL:O/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 | 6.0 |
| Attack Vector (AV) | Local (L) |
| Attack Complexity (AC) | High (H) |
| Privileges Required (PR) | Low (L) |
| User Interaction (UI) | Required (R) |
| Scope (S) | Unchanged (U) |
| Confidentiality (C) | None (N) |
| Integrity (I) | High (H) |
| Availability (A) | High (H) |
| Temporal Score (Overall) | 5.4 |
| 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:U/C:N/I:H/A:H/E:P/RL:O/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.
