First Published: April 14, 2021
CVE Information: |
Impact of Vulnerabilities: |
Low – see the Vulnerability Description section below |
CVE IDs |
Severity Rating |
CVSS v3.1
Base Score |
Affected Products |
Impact of Vulnerabilities |
CVE-2021-3450 |
High |
7.4 |
See the Product Vulnerability Status table below |
CWE-295 – Improper Certificate Validation |
CVE-2021-3449 |
Medium |
5.9 |
See the Product Vulnerability Status table below |
CWE-476 – NULL Pointer Dereference |
Highest CVSS v3.1 Base Score: |
High |
Recommendations: |
Deploy the fixes as they are made available. |
Security Bulletin Replacement: |
None |
Affected Models: |
See the Product Vulnerability Status table below for platform details. |
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
OpenSSL released a security advisory against version 1.1.1 with 1.1.1k containing the fix. Some products use 1.0.2 (with an extended Support contract) and are not vulnerable.
- CVE-2021-3150
The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).
https://nvd.nist.gov/vuln/detail/CVE-2021-3450
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450
- CVE-2021-3149
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).
https://nvd.nist.gov/vuln/detail/CVE-2021-3449
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449
Product Vulnerability Status
This Security Bulletin will be updated as additional information is available.
Update Availability |
Product |
Version |
CVE-2021-3450 and CVE-2021-3449 |
Vulnerable and Updated |
Skyhigh Web Gateway (SWG) |
All |
10.1.1, 8.2.19 |
SWG (Cloud) |
All |
10.1.1, 8.2.19 |
Not Vulnerable |
Advanced Threat Defense (ATD) |
All |
|
Appliance Data Monitor (ADM) |
All |
|
Data Exchange Layer (DXL) Broker |
All |
|
Data Loss Prevention (DLP)
Prevent and Monitor |
All |
|
McAfee Active Response (MAR) Server |
All |
|
Network Security Manager (NSM) Linux |
All |
|
Network Security Platform (NSP) |
All |
|
Network Threat Behavior Analysis (NTBA) |
All |
|
SIEM Enterprise Security Manager |
All |
|
Threat Intelligence Exchange (TIE) Server |
All |
|
Remediation
To remediate this issue, go to the
Product Downloads site, and download the applicable product update/hotfix file:
Product |
Version |
Type |
Release Date |
SWG |
10.1.1,
8.2.19 |
Update |
April 14, 2021 |
SWG (Cloud) |
10.1.1,
8.2.19 |
Update |
April 14, 2021 |
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.
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 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.
For ePO/server products:
Use the following instructions for server-based products:
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.
For DLPe ePO Extension:
Use the following instructions:
- Log on to the ePO server.
- Click Menu, Data Protection, DLP Policy.
- Inside the DLP console click Help, About. 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.
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.
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
- 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.