Knowledge Center

McAfee Security Bulletin - Data Exchange Layer update fixes three vulnerabilities (CVE-2018-5391, CVE-2018-15473, and CVE-2018-0737)
Security Bulletins ID:   SB10266
Last Modified:  5/7/2019


First Published: January 25, 2018
 Impact of Vulnerability: Denial of Service (CWE-730, OWASP 2004:A9)
Information Leak/Disclosure (CWE-717, OWASP 2004:A6)
 CVE ID: CVE-2018-5391
 Severity Rating: CVE-2018-5391: High
CVE-2018-15473: Medium
CVE-2018-0737: Medium
 CVSS v3 Base/Temporal Scores: CVE-2018-5391: 7.5 / 7.0
CVE-2018-15473: 5.3 / 4.9
CVE-2018-0737: 5.9 / 5.5
 Recommendations: Install or update to Data Exchange Layer (DXL) Broker Platform:
  • 4.0.0 Hotfix 9 (HF9)
  • 4.1.2 Hotfix 1 (HF1)
 Security Bulletin Replacement: None
 Affected Software: DXL Broker Platform:
  • 4.0.x earlier than 4.0.0 HF9
  • 4.1.x earlier than 4.1.2 HF1
 Location of updated software: http://www.mcafee.com/us/downloads/downloads.aspx
To receive email notification when this Security Bulletin is updated, click Subscribe on the right side of the page. You must be logged in to subscribe.
Article contents: Vulnerability Description
This DXL release updates multiple libraries on the DXL Broker Appliance to address security issues in the libraries installed on the appliance.

This update resolves the following issues:
  1. CVE-2018-5391
    The Linux kernel, versions 3.9+, is vulnerable to a denial-of-service attack with low rates of specially modified packets targeting IP fragment re-assembly. An attacker may cause a denial of service condition by sending specially crafted IP fragments. Various vulnerabilities in IP fragmentation have been discovered and fixed over the years. The current vulnerability (CVE-2018-5391) became exploitable in the Linux kernel with the increase of the IP fragment reassembly queue size.
  2. CVE-2018-15473
    OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.
  3. CVE-2018-0737
    The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o).
Affected Components:
McAfee DXL Broker Appliance
  • Linux Kernel
  • OpenSSH
  • OpenSSL
To remediate this issue, update the DXL Broker Platform to 4.1.2 HF1.

Go to the Product Downloads site, and download the applicable product hotfix file:
Product Version Type File Name Release Date
DXL   4.1.2 HF1 Hotfix DXL Platform 4.1.2 HF1 January 23, 2018
DXL  4.0.0 HF9 Hotfix DXL Platform 4.0.0 Hotfix9 May 7, 2019
Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, updates, and hotfixes. Review the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions on how to install these updates.
None. McAfee highly recommends that all customers upgrade the DXL Broker Platform to 4.1.2 HF1.
These vulnerabilities were first disclosed by The MITRE Corporation as a CVE.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable or not?
For Appliances:
Use the following instructions for DXL Broker Appliances:
  1. Connect to the DXL Broker Appliance through SSH.
  2. Check that the installed version of the dxlplatform package is or later.
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: 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 the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
  1. CVE-2018-5391
    Base Score 7.5
    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) High (H)
    Temporal Score (Overall) 7.0
    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.
  2. CVE-2018-15473
    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) Low (L)
    Integrity (I) None (N)
    Availability (A) None (N)
    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.
  3. CVE-2018-0737
    Base Score 5.9
    Attack Vector (AV) Network (N)
    Attack Complexity (AC) High (H)
    Privileges Required (PR) None (N)
    User Interaction (UI) None (N)
    Scope (S) Unchanged (U)
    Confidentiality (C) High (H)
    Integrity (I) None (N)
    Availability (A) None (N)
    Temporal Score (Overall) 5.5
    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.
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our external PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Security Bulletins. 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 McAfee?
If you have information about a security issue or vulnerability with a McAfee product, visit the McAfee PSIRT website for instructions at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Report a Security Vulnerability.
How does McAfee respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found in any McAfee 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.
McAfee only publishes 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.
View our PSIRT policy on the McAfee PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > About PSIRT.
To contact Technical Support, log on to the ServicePortal and go to the Create a Service Request page at https://support.mcafee.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.
The information provided in this Security Bulletin is provided as is without warranty of any kind. McAfee disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if McAfee or its suppliers have been advised of the possibility of such damages. Some states do not 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 should not 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 are not 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 remains at our sole discretion and may be changed or canceled at any time.

Rate this document

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.