Security Bulletin - McAfee Agent and Host Intrusion Prevention update addresses DLL Search Order Hijacking vulnerability (CVE-2019-3613 and CVE-2020-7279)
Security Bulletins ID:
SB10320
Last Modified: 2022-05-04 16:56:51 Etc/GMT
Last Modified: 2022-05-04 16:56:51 Etc/GMT
Summary
First Published: June 9, 2020
Article contents:
To remediate this issue, install the updates shown in the table below for your products.
For MA:
Customers should update to 8.0.0 Patch 15.
Go to the Product Downloads site, and download the applicable product update file:
NOTE: Subsequent MA releases are cumulative and contain this security fix.
Download and Installation Instructions
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.
Acknowledments
CVE-2019-3613 - We credit Julian Horoszkiewicz (ATOS CERT) for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about 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, visit the CVSS website at: https://www.first.org/cvss/.
When calculating CVSS 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 the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
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
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.
Impact of Vulnerability: | Privilege Escalation Vulnerability (CWE-274) |
CVE ID: | CVE-2019-3613 CVE-2020-7279 |
Severity Rating: | Medium |
CVSS v3 Base/Temporal Scores: | CVE-2019-3613: 5.9 / 5.3 CVE-2020-7279: 4.6 / 4.2 |
Recommendations: | Install or update to:
|
Security Bulletin Replacement: | None |
Affected Software: | MA:
|
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:
- Vulnerability Description
- Remediation
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
- CVE-2019-3613
DLL Search Order Hijacking vulnerability in McAfee Agent (MA) prior to 5.6.4 allows attackers with local access to execute arbitrary code via execution from a compromised folder.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3613
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3613
- CVE-2020-7279
DLL Search Order Hijacking Vulnerability in the installer component of Host Intrusion Prevention System (Host IPS) for Windows prior to 8.0.0 Patch 15 Update allows attackers with local access to execute arbitrary code via execution from a compromised folder.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-7279
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7279
To remediate this issue, install the updates shown in the table below for your products.
For MA:
- Customers on 5.6.x should update to 5.6.4 or later.
- Customers on 5.5.x should upgrade to 5.6.4 or update to 5.5.4 or later.
- Customers on earlier versions of 5.x should upgrade to 5.6.4 or 5.5.4 or later.
Customers should update to 8.0.0 Patch 15.
Go to the Product Downloads site, and download the applicable product update file:
Product | Version | Type | File Name | Release Date |
MA for Windows | 5.6.4 | Update | MA564WIN.zip MA564WIN_EMBEDDED.zip |
March 10, 2020 |
MA for Windows | 5.5.4 | Update | MA544WIN.zip MA544WIN_EMBEDDED.zip |
March 10, 2020 |
Host IPS for Windows | 8.0.0 Patch 15 | Update | N/A | June 9, 2020 |
NOTE: Subsequent MA releases are cumulative and contain this security fix.
Download and Installation Instructions
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.
Acknowledments
CVE-2019-3613 - We credit Julian Horoszkiewicz (ATOS CERT) for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
- Right-click on the McAfee tray shield icon on the Windows taskbar.
- Select Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. The product version displays.
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about 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, visit the CVSS website at: https://www.first.org/cvss/.
When calculating CVSS 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 the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
- CVE-2019-3613: DLL search order hijacking in MA
Base Score 5.9 Attack Vector (AV) Local (L) Attack Complexity (AC) Low (L) Privileges Required (PR) Low (L) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) None (N) Integrity (I) High (H) Availability (A) None (N) Temporal Score (Overall) 5.3 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N/E:P/RL:O/RC:C&version=3.1
- CVE-2020-7279: DLL search order hijacking in Host IPS
Base Score 4.6 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) Low (L) Integrity (I) High (H) Availability (A) None (N) Temporal Score (Overall) 4.2 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:N/E:P/RL:O/RC:C&version=3.1
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.