Security Bulletin - McAfee Agent for Windows update fixes two vulnerabilities (CVE-2021-31839 and CVE-2021-31840)
Security Bulletins ID:
SB10362
Last Modified: 2022-05-04 19:27:14 Etc/GMT
Last Modified: 2022-05-04 19:27:14 Etc/GMT
Summary
First Published: June 8, 2021
Product: | Impacted Versions: | CVE ID: | Impact of Vulnerabilities: | Severity Ratings: | CVSS v3.1 Base/Temporal Scores: |
McAfee Agent (MA) for Windows | 5.x prior to 5.7.3 | CVE-2021-31839 | CWE-269: Improper Privilege Management | Medium | 4.8 / 4.3 |
MA for Windows | 5.x prior to 5.7.3 | CVE-2021-31840 | CWE-427: Uncontrolled search path element | High | 7.3 / 6.6 |
Recommendations: | Install or update to MA for Windows 5.7.3 | ||||
Security Bulletin Replacement: | None | ||||
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
- CVE-2021-31839
Improper privilege management vulnerability in McAfee Agent for Windows prior to 5.7.3 allows a local user to modify event information in the MA event folder. This allows a local user to either add false events or remove events from the event logs prior to them being sent to the ePO server.
This folder is intended to be accessible to third-party products which are integrated with ePO. Permissions have been updated to only allow authorized third-party products access to this folder.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31839
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31839
- CVE-2021-31840
A vulnerability in the preloading mechanism of specific dynamic link libraries in McAfee Agent for Windows prior to 5.7.3 could allow an authenticated, local attacker to perform a DLL preloading attack with unsigned DLLs. To exploit this vulnerability, the attacker would need to have valid credentials on the Windows system. This would result in the user gaining elevated permissions and being able to execute arbitrary code.
The vulnerability is due to insufficient validation of the resources loaded by the application at run time. An attacker could exploit this vulnerability by crafting a malicious DLL file and placing it in a specific location on the targeted system.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31840
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31840
To remediate this issue, customers using MA for Windows should update to 5.7.3.
Go to the Product Downloads site, and download the applicable product update file:
Product | Version | Type | Release Date |
MA for Windows | 5.7.3 | Update | June 8, 2021 |
Download and Installation Instructions
For instructions to download McAfee product updates and hotfixes, see: KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable or not?
For endpoint products:
Use the following instructions for endpoint or client-based products:
- Right-click 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 server-based products:
- Check the version and build of ePO that is installed. For instructions, see: KB52634 - How to determine what update is installed for ePO.
- Create a query in ePO for the product version of the product installed within your organization.
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.
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-2021-31839: Incorrect permissions on MA for Windows event folder
Base Score 4.8 Attack Vector (AV) Local (L) Attack Complexity (AC) Low (L) Privileges Required (PR) Low (L) User Interaction (UI) Required (R) Scope (S) Unchanged (U) Confidentiality (C) Low (L) Integrity (I) Low (L) Availability (A) Low (L) Temporal Score (Overall) 4.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:U/C:L/I:L/A:L/E:P/RL:O/RC:C&version=3.1
- CVE-2021-31840: DLL preload vulnerability in MA for Windows
Base Score 7.3 Attack Vector (AV) Local (L) Attack Complexity (AC) Low (L) Privileges Required (PR) Low (L) User Interaction (UI) Required (R) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 6.6 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:U/C:H/I:H/A:H/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, log on to the ServicePortal and go to the Create a Service Request page at https://supportm.trellix.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.
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.