Security Bulletin - Trellix Application and Change Control ePO extension fixes one vulnerability (CVE-2023-5607)
Security Bulletins ID:
SB10411
Last Modified: 2023-11-27 09:25:47 Etc/GMT
Last Modified: 2023-11-27 09:25:47 Etc/GMT
Summary
First Published: November 27, 2023
Article contents:
The TACC ePO extension offers the ability for an authorised administrator to access the "Inventory" section of the ePO extension and upload custom GTI ratings through the Import GTI ratings option. There's an error in the parsing logic, which allows a zip file to be uploaded that utilizes path traversal in the archive file paths to trigger remote code execution on the ePO server. This is only applicable to on-premises ePO servers.
The risk of exploitation can be reduced by limiting access to the ePO interface through network access controls, restricting the number of users, and granting only the required level of access to perform the required tasks. It's recommended that the interface for your ePO server isn't placed on the internet, allowing only access from trusted networks.
CVE-2023-5607:
An improper limitation of a path name to a restricted directory (path traversal) vulnerability in the TACC ePO extension, for on-premises ePO servers, prior to version 8.4.0 could lead to an authorised administrator attacker executing arbitrary code through uploading a specially crafted GTI reputation file. The attacker would need the appropriate privileges to access the relevant section of the User Interface. The import logic has been updated to restrict file types and content.
Remediation
Customers on TACC 8.3.8.x and earlier should update their ePO extension to 8.4.0.
The 8.4.0 ePO extension can manage agents from an earlier release.
The 8.4.0 agent will be released separately, and will be managed by this extension.
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 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.
Acknowledgments
Trellix credits@g00dh4ck3r for responsibly reporting these vulnerabilities.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For Endpoint Security (ENS) on Windows:
Use the following instructions for endpoint or client-based products:
Use the following instructions for endpoint or client-based products:
Use the following instructions for server-based products:
Use the following instructions for Appliance-based products:
Use the following instructions:
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 determine how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.
When calculating CVSS scores, we adopt 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.
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
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.
| Product | Impacted Versions | CVE ID | Impact of Vulnerabilities | Severity Ratings | CVSS v3.1 Base/Temporal Scores |
| Trellix Application and Change Control (TACC) | Prior to version 8.4.0 | CVE-2023-5607 | CWE-22: Improper limitation of a path name to a restricted directory (path traversal) | High | 8.4 |
| Recommendations | Update the ePolicy Orchestrator (ePO) extension to 8.4.0 | ||||
| Security Bulletin Replacement | None | ||||
| 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
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
The TACC ePO extension offers the ability for an authorised administrator to access the "Inventory" section of the ePO extension and upload custom GTI ratings through the Import GTI ratings option. There's an error in the parsing logic, which allows a zip file to be uploaded that utilizes path traversal in the archive file paths to trigger remote code execution on the ePO server. This is only applicable to on-premises ePO servers.
The risk of exploitation can be reduced by limiting access to the ePO interface through network access controls, restricting the number of users, and granting only the required level of access to perform the required tasks. It's recommended that the interface for your ePO server isn't placed on the internet, allowing only access from trusted networks.
CVE-2023-5607:
An improper limitation of a path name to a restricted directory (path traversal) vulnerability in the TACC ePO extension, for on-premises ePO servers, prior to version 8.4.0 could lead to an authorised administrator attacker executing arbitrary code through uploading a specially crafted GTI reputation file. The attacker would need the appropriate privileges to access the relevant section of the User Interface. The import logic has been updated to restrict file types and content.
Remediation
Customers on TACC 8.3.8.x and earlier should update their ePO extension to 8.4.0.
The 8.4.0 ePO extension can manage agents from an earlier release.
The 8.4.0 agent will be released separately, and will be managed by this extension.
To remediate this issue, go to the Product Downloads site, and download the applicable product update/hotfix file:
| Product | Version | Type | Release Date |
| TACC ePO extension | 8.4.0 | Minor | November 27, 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.
Acknowledgments
Trellix credits
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For Endpoint Security (ENS) on Windows:
Use the following instructions for endpoint or client-based products:
- Right-click the tray shield icon on the Windows taskbar.
- Select Endpoint Security.
- In the console, select Action Menu.
- In the Action Menu, select About. The product version displays.
Use the following instructions for endpoint or client-based products:
- Right-click the 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 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.
Use the following instructions for Appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version displays.
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.
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 determine how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.
When calculating CVSS scores, we adopt 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.
What are the CVSS scoring metrics?
- CVE-2022-21675: Zip Slip vulnerability
Base Score 8.4 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) High (H) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 7.6 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: This CVSS version 3.1 vector was used to generate this score.
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.
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.
