Security Bulletin - Multiple product updates fix OpenSSL vulnerabilities (CVE-2019-1559)
Security Bulletins ID:
SB10282
Last Modified: 2022-05-04 15:43:10 Etc/GMT
Last Modified: 2022-05-04 15:43:10 Etc/GMT
Summary
First Published: May 14, 2019
Article contents:
The main issue addressed in the OpenSSL 1.0.2r release relates to calling SSL_shutdown() twice. None of our products explicitly make this sequence of calls. We are updating our versions of OpenSSL for those products that might be vulnerable.
To remediate this issue, go to the Product Downloads site, and download the applicable product update/hotfix file:
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.
Product Specific Notes
TIE Server: See KB90843 for instructions on how to update OpenSSL.
Acknowledgments
This vulnerability was first disclosed by The MITRE Corporation as a CVE.
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.
For Appliances:
Use the following instructions for Appliance-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?
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: | 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: | 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
- Product Specific Notes
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
The main issue addressed in the OpenSSL 1.0.2r release relates to calling SSL_shutdown() twice. None of our products explicitly make this sequence of calls. We are updating our versions of OpenSSL for those products that might be vulnerable.
- 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.
https://nvd.nist.gov/vuln/detail/CVE-2019-1559
- 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.
https://eyalro.net/project/cat/
https://github.com/openssl/openssl/issues/7739
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 openssl-libs-1.0.2r-1.mlos2.x86_64.rpm |
February 28, 2019 |
| Web Gateway | 7.7.2.21 | Main Release | mwgappl-7.7.2.21.0-28544-x.86_64.iso | April 9, 2019 |
| Web Gateway | 7.8.2.8 | Main Release | mwgappl-7.8.2.8.0-28536-x.86_64.iso | 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 MA561LNX.zip MA561MAC.zip MA561WIN_EMBEDDED.zip |
May 14, 2019 |
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.
Product Specific Notes
TIE Server: See KB90843 for instructions on how to update OpenSSL.
Acknowledgments
This vulnerability was first disclosed by The MITRE Corporation as a CVE.
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.
For Appliances:
Use the following instructions for Appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version displays.
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-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.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?name=CVE-2019-1559&vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- 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.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
