First Published: February 22, 2023
 

CVE Information
CVE IDs	Severity Rating	Impacted Products	Impact of Vulnerabilities	CVSS v3.1 Base Scores
CVE-2023-0286	High	See table below	CWE-843: Type confusion	High
CVE-2022-4304	Medium	See table below	CWE-208:Observable Timing Discrepancy	Medium
CVE-2023-0215	Medium	See table below	CWE-135:Out-of-bounds read	Medium
CVE-2022-4450	Medium	See table below	CWE-415:Double free	Medium
Highest CVSS v3.1 Base Score:		High
Recommendations:		Deploy product fixes as they are made available.
Security Bulletin Replacement:		None.
Affected products and versions:		See the Trellix/Skyhigh Security Product Vulnerability Status table below for platform details. For our general response see: KB96301 Trellix response to the February 7, 2023 OpenSSL Security Advisory
Location of updated software:		Product Downloads site

NOTE: The following CVEs are also listed in the February 7th, 2023 OpenSSL Security advisory but none of them apply to any Trellix or Skyhigh products: CVE-2022-4203, CVE-2023-0216, CVE-2023-0217 and CVE-2023-0401



Article contents:

• Vulnerability Description
• Trellix and Skyhigh Security Product Vulnerability Status
• Remediation
• Frequently Asked Questions (FAQs)
• Resources
• Disclaimer

Vulnerability Description

CVE-2023-0286
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName.
X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE.
This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.
When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call,
enabling them to read memory contents or enact a denial of service.
In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature.
If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon.
As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network. 

National Vulnerability Database CVE-2023-0286

cve.mitre.org CVE-2023-0286 


CVE-2022-4304
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption, an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. 
For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. 

National Vulnerability Database CVE-2022-4304

cve.mitre.org CVE-2022-4304 


CVE-2022-4450
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data.
If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data.
The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash.
This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.

National Vulnerability Database CVE-2022-4450

cve.mitre.org CVE-2022-4450


CVE-2023-0215
The public API function BIO_new_NDEF is a helper function used for streaming 
ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. 
The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. 
This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO.
This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. 
Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.  

National Vulnerability Database CVE-2023-0215
 
cve.mitre.org CVE-2023-0215


Trellix/Skyhigh Security Product Vulnerability Status   
Not vulnerable

Trellix products: 

• Trellix Active Response (AR) Client  
• Trellix Active Response (AR) Cloud 
• Trellix Active Response (AR) Server 
• Trellix Application and Change Control (ACC) for Linux  
• Trellix Application and Change Control (ACC) for Windows  
• Trellix Cloud Bridge 
• Trellix Cloud Multi-Vector Virtual Execution (Cloud MVX) 
• Trellix Cloud Workload Security (CWS) 
• Trellix Data Exchange Layer (DXL) Broker  
• Trellix Data Exchange Layer (DXL) Client 
• Trellix Data Loss Prevention (DLP) Discover  
• Trellix Data Loss Prevention (DLP) Endpoint for Mac  
• Trellix Data Loss Prevention (DLP) Endpoint for Windows  
• Trellix Data Loss Prevention (DLP) Monitor  
• Trellix Data Loss Prevention (DLP) Prevent  
• Trellix Database Security (DBSec) 
• Trellix Drive Encryption (DE)  
• Trellix Email Security – Cloud 
• Trellix Endpoint Security (ENS) for Linux   
• Trellix Endpoint Security (ENS) for Mac  
• Trellix Endpoint Security (ENS) for Windows  
• Trellix Endpoint Security for Storage Protection (ENSSP)  
• Trellix Endpoint Upgrade Assistant  
• Trellix ePolicy Orchestrator (ePO) Cloud 
• Trellix ePolicy Orchestrator (ePO) Agent Handler  
• Trellix File and Removable Media Protection (FRP)  
• Trellix Helix 
• Trellix Host Intrusion Prevention (HIPS)  
• Trellix Identity Access Management (IAM) 
• Trellix Insights 
• Trellix Intelligent Sandbox 
• Trellix Investigation Analysis (IA) 
• Trellix Logon Collector 
• Trellix Management of Native Encryption (MNE)  
• Trellix Management for Optimized Virtual Environments (MOVE) AntiVirus  
• Trellix Endpoint 
• Trellix Endpoint Detection Response (EDR) Client  
• Trellix Intrusion Prevention System Manager
• Trellix Intrusion Prevention System Sensor
• Trellix Mobile Security 
• Trellix Network Threat Behavior Analysis (NTBA)  
• Trellix Packet Capture (PX) 
• Trellix Rogue System Detection (RSD)  
• Trellix Security for Microsoft Exchange (SME)  
• Trellix Security for Microsoft SharePoint (SMS)  
• Trellix Security Orchestrator (SO) 
• Trellix Threat Intelligence Exchange (TIE) 
• Trellix Virtual Intrusion Prevention System 
• Trellix VirusScan Command Line Scan (VSCL)  
• Trellix Virus Scan Enterprise (VSE)  
• Trellix VirusScan Enterprise Linux (VSEL)  
• Trellix VirusScan Enterprise for Storage (VSES)  
• Trellix VirusScan for Mac 
• Trellix XPOD 

Skyhigh Security products:

• CASB 
• Client Proxy (SCP) for Mac  
• Client Proxy (SCP) for Windows  
• Content Security Reporter  
• Cloud Connector 
• Cloud Infrastructure (CNAPP/CSPM/CWPP) 
• Data Protection 
• Private Access 
• Remote Browser Isolation 
• Secure Web Gateway (SWG) - Cloud 
• Secure Web Gateway (SWG) – On Prem 

Remediation

To remediate this issue, go to the Product Documentation site, and download the applicable product update/hotfix files.

Product	Version	Type	Release Date	Notes
Trellix Enterprise Security Manger (SIEM)	11.6.3	Update	March 15, 2023
Trellix Agent	5.7.9	Update	March 30, 2023
ePO - On Premise	5.10.0 Service Pack 1	Update	April 4, 2023

Download and Installation Instructions
For instructions to download product updates and hotfixes, see: KB56057 - How to download product updates and documentation.
Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.

Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For Endpoint Security on Windows:
Use the following instructions for endpoint or client-based products:

1. Right-click the tray shield icon on the Windows taskbar.
2. Select Endpoint Security.
3. In the console, select Action Menu.
4. In the Action Menu, select About. The product version displays.

For endpoint products and ENS on other platforms:
Use the following instructions for endpoint or client-based products:

1. Right-click the 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/server products:
Use the following instructions for server-based products:

• Check the version and build of ePO that is installed. For instructions, see: KB52634 - How to determine what hotfix is installed for ePO.
• Create a query in ePO for the product version of the product installed within your organization.

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.

For DLPe ePO Extension:
Use the following instructions:

1. Log on to the ePO server.
2. Click Menu, Data Protection, DLP Policy.
3. Inside the DLP console click Help, About. The product version displays.

What is CVSS?
Common Vulnerability Scoring System (CVSS) 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 have 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 don’t 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.