Security Bulletin - McAfee Agent update fixes a vulnerability in handling UDP requests (CVE-2019-3598)
Security Bulletins ID:
SB10272
Last Modified: 2022-05-04 15:38:58 Etc/GMT
Last Modified: 2022-05-04 15:38:58 Etc/GMT
Summary
First Published: February 26, 2019
Article contents:
McAfee Agent handles UDP requests through a configured port as part of its normal operation. A specially crafted UDP packet might allow an attacker on the same subnet to cause a partial denial-of-service in one of the McAfee Agent components.
This update resolves the following issue:
CVE-2019-3598
Buffer Access with Incorrect Length Value in McAfee Agent (MA) 5.x allows remote unauthenticated users to potentially cause a partial denial-of-service via specifically crafted UDP packets.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3598
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3598
Affected Component:
To remediate this issue:
For products that include an affected version of McAfee Agent for MLOS in their image, see the table below for the remediated version of the product:
1 For TIE Server upgrades, MA is not updated. For fresh installations, the updated version of MA is included. The MA for MLOS package is available on the Product Downloads site. The package is available under the TIE 2.3.0 section for both 2.2.0 HF1 and 2.3.0 installations – McAfee Agent for MLOS Version 5.5.1.462. See KB85586 for instructions on how to update MA through ePO.
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 the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Acknowledgments
We credit Frank Cozijnsen from KPN RED-team for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Windows Endpoint products:
Use the following instructions for endpoint or client-based 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, visit the CVSS website at: http://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-3598: Denial-of-service vulnerability
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:F/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
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: | Buffer Access with Incorrect Length Value (CWE-805) |
CVE ID: | CVE-2019-3598 |
Severity Rating: | Medium |
CVSS v3 Base/Temporal Scores: | 5.3 / 4.9 |
Recommendations: | Install or update to one of the following McAfee Agent (MA) versions:
|
Security Bulletin Replacement: | None |
Affected Software: | MA versions:
|
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
McAfee Agent handles UDP requests through a configured port as part of its normal operation. A specially crafted UDP packet might allow an attacker on the same subnet to cause a partial denial-of-service in one of the McAfee Agent components.
This update resolves the following issue:
CVE-2019-3598
Buffer Access with Incorrect Length Value in McAfee Agent (MA) 5.x allows remote unauthenticated users to potentially cause a partial denial-of-service via specifically crafted UDP packets.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3598
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3598
Affected Component:
- McAfee Agent Common Service
To remediate this issue:
- Upgrade MA 5.6.0 to 5.6.1.
- Upgrade MA 5.5.1 and earlier to 5.5.1 HF1267991 or 5.6.1.
- Upgrade MA 5.0.6 and earlier to 5.0.6 HF1267994, 5.5.1 HF1267991, or 5.6.1.
- See the second table below if you use an appliance that consumes the McAfee Agent for McAfee Linux Operating System (MLOS).
Product | Version | Type | File Name | Release Date |
MA | 5.6.1 | Update | MA561WIN.zip MA561LNX.zip MA561MAC.zip MA561WIN_EMBEDDED.zip |
May 14, 2019 |
MA | 5.5.1 | Hotfix | MA551HF1267991LNX.zip MA551HF1267991MAC.zip MA551HF1267991WIN.zip MA551HF1267991WIN_EMBEDDED.zip |
March 21, 2019 |
MA | 5.0.6 | Hotfix | MA506HF1267994LNX.zip MA506HF1267994MAC.zip MA506HF1267994WIN.zip MA506HF1267994WIN_EMBEDDED.zip |
March 21, 2019 |
For products that include an affected version of McAfee Agent for MLOS in their image, see the table below for the remediated version of the product:
Product | Version | Type | File Name | Release Date |
Data Exchange Layer (DXL) Broker | 4.0.x 4.1.x 5.0.x |
Hotfix | DXL Platform 5.0.1 Hotfix 2 | April 9, 2019 |
DXL Broker | 4.0.x 4.1.x |
Hotfix | DXL Platform 4.1.2 Hotfix 3 | April 9, 2019 |
DXL Broker | 4.0.x | Hotfix | DXL Platform 4.0.0 Hotfix 9 | May 7, 2019 |
Data Loss Prevention (DLP) Monitor/Prevent | 11.x 10.x |
Minor | DLP Monitor/Prevent 11.3.0 | July 23, 2019 |
DLP Monitor/Prevent | 11.1.x 11.0.x 10.x |
Update | DLP Monitor/Prevent 11.1.200 | July 23, 2019 |
DLP Monitor/Prevent | 11.0.x | Hotfix | DLP Monitor/Prevent 11.0.701 | July 23, 2019 |
DLP Prevent | 10.x | Hotfix | DLP Prevent 10.0.303 | July 23, 2019 |
Threat Intelligence Exchange (TIE) Server | 2.0.x 2.1.x 2.2.x 2.3.x |
Hotfix | TIE Server 2.3.1 Hotfix 11 | April 9, 2019 |
TIE Server | 2.0.x 2.1.x 2.2.x |
Hotfix | TIE Server 2.2.0 Hotfix 11 | April 23, 2019 |
1 For TIE Server upgrades, MA is not updated. For fresh installations, the updated version of MA is included. The MA for MLOS package is available on the Product Downloads site. The package is available under the TIE 2.3.0 section for both 2.2.0 HF1 and 2.3.0 installations – McAfee Agent for MLOS Version 5.5.1.462. See KB85586 for instructions on how to update MA through ePO.
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 the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Acknowledgments
We credit Frank Cozijnsen from KPN RED-team for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Windows Endpoint products:
Use the following instructions for endpoint or client-based products:
- Right-click the McAfee tray shield icon on the Windows taskbar.
- Select About. The product version displays.
Use the following instructions for endpoint or client-based products:
- Open a terminal.
- Enter the following command:
- For Linux: /opt/McAfee/agent/bin/cmdagent -i
- For Mac: /Library/McAfee/agent/bin/cmdagent -i
- For Windows: C:\Program Files\McAfee\Agent\cmdagent -i
The product version displays in the output.
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: http://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-3598: Denial-of-service vulnerability
Base Score | 5.3 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | Low (L) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | None (N) |
Integrity (I) | None (N) |
Availability (A) | Low (L) |
Temporal Score (Overall) | 4.9 |
Exploitability (E) | Functional (F) |
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://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:F/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.