McAfee Security Bulletin - Multiple McAfee product updates fix OpenSSL vulnerabilities (CVE-2019-1559)
Boletines de seguridad ID:   SB10282
Última modificación:  5/29/2019


First Published: May 14, 2019
 Impact of Vulnerability: Information Leak/Disclosure (CWE-717, OWASP 2004:A6)
 CVE ID: CVE-2019-1559
 Severity Rating: CVE-2019-1559: Medium
PKCS#1 padding oracle: Medium
 CVSS v3 Base/Temporal Scores: CVE-2019-1559: 5.9
PKCS#1 padding oracle: 5.9
 Recommendations: Deploy product updates as they are made available
 Security Bulletin Replacement: None
 Affected Software: Data Exchange Layer (DXL) 4.x, 5.x
McAfee Agent 5.6.x
Threat Intelligence Exchange (TIE) Server 2.x
Web Gateway 7.x, 8.x
 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 on to subscribe.

Article contents: Vulnerability Description
The main issue addressed in the OpenSSL 1.0.2r release relates to calling SSL_shutdown() twice. None of the McAfee products explicitly make this sequence of calls. We are updating our versions of OpenSSL for those products that may be vulnerable.
  1. CVE-2019-1559: 0-byte record padding oracle   
    If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one), OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, this amounts to a padding oracle that could be used to decrypt data. For this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimized implementations of certain commonly used ciphersuites.
  2. PKCS#1 padding oracle
    A Bleichenbacher type side-channel based padding oracle attack was found in the way OpenSSL 1.0.2 before 1.0.2r, 1.1.0 before 1.1.0k, and 1.1.1 before 1.1.1b handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.
    OpenSSL did not publish a CVE for this issue, which is fixed in the same release as CVE-2019-1559.
To remediate this issue, go to the Product Downloads site, and download the applicable product update/hotfix file:
Product Versions Type File Name Release Date
TIE Server 2.x Patch openssl-1.0.2r-1.mlos2.x86_64.rpm
February 28, 2019
Web Gateway Main Release mwgappl- April 9, 2019
Web Gateway Main Release mwgappl- April 9, 2019
Web Gateway 8.1.1 Controlled Release mwgappl-8.1.1-28538.x.86_64.iso April 9, 2019
DXL 5.0 Hotfix Data Exchange Layer 5.0.01 HF3 May 7, 2019
DXL 4.0 Hotfix Data Exchange Layer 4.0.0 HF9 May 7, 2019
McAfee Agent 5.6.1 Update MA561WIN.zip
May 14, 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.
Product Specific Notes
TIE Server: See KB90843 for instructions on how to update OpenSSL.
This vulnerability was 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 Endpoint products:
Use the following instructions for endpoint or client-based products:
  1. Right-click on the McAfee tray shield icon on the Windows taskbar.
  2. Select Open Console.
  3. In the console, select Action Menu.
  4. In the Action Menu, select Product Details. The product version displays.
For ePO:
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.

For Appliances:
Use the following instructions for Appliance-based products:
  1. Open the Administrator's User Interface (UI).
  2. Click the About link. The product version displays.
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-2019-1559: 0-byte record padding oracle
    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)
    NOTE: The below CVSS version 3.0 vector was used to generate this score.
  2. PKCS#1 padding oracle
    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)
    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?
McAfee's key priority is the security of our customers. If a vulnerability is found within any of McAfee's 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.

Calificar este documento

Glosario de términos técnicos

 Resaltar los términos del glosario

Tómese un momento para consultar nuestro Glosario de términos técnicos.