Trellix Security Bulletin – Trellix Threat Intelligence Exchange 4.0.0 HF2 fixes the vulnerability CVE-2023-22809
Security Bulletins ID:
SB10401
Last Modified: 2023-04-11 13:28:55 Etc/GMT
Last Modified: 2023-04-11 13:28:55 Etc/GMT
Summary
First Published: April 11, 2023
Article contents:
Remediation
To prevent a user-specified editor from being utilised by sudoedit you may add the following line to the sudoers file:
To restrict the editor when editing specific files, a Cmnd_Alias can be used, for example:
However, we recommend upgrading to the current stable release sudo 1.9.13p3 released on March 6, 2023.
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.
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:
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 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.
What are the CVSS scoring metrics?
CVE-2023-22809: sudo: arbitrary file write with privileges.
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
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.
| Product: | Impacted Versions: | CVE ID: | Impact of Vulnerabilities: | Severity Ratings: | CVSS v3.1 Base/Temporal Scores: |
| Trellix Threat Intelligence Exchange (TIE) | 4.0.0 and earlier | CVE-2023-22809 | CWE-269 - Improper Privilege Management | High | 7.8/7.0 |
| Recommendations: | Install or update to version 4.0.0 or later. | ||||
| 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
- Product Specific Notes
- Frequently Asked Questions (FAQs)
- Disclaimer
CVE-2023-22809: sudo: arbitrary file write with privileges.
In Sudo before 1.9.12p2, the sudoedit feature mishandles extra arguments passed in the user-provided environment variables (SUDO_EDITOR, VISUAL, and EDITOR),
allowing a local attacker to append arbitrary entries to the list of files to process. This can lead to privilege escalation.
In Sudo before 1.9.12p2, the sudoedit feature mishandles extra arguments passed in the user-provided environment variables (SUDO_EDITOR, VISUAL, and EDITOR),
allowing a local attacker to append arbitrary entries to the list of files to process. This can lead to privilege escalation.
Remediation
To prevent a user-specified editor from being utilised by sudoedit you may add the following line to the sudoers file:
Defaults!sudoedit env_delete+="SUDO_EDITOR VISUAL EDITOR"
To restrict the editor when editing specific files, a Cmnd_Alias can be used, for example:
Cmnd_Alias EDIT_MOTD = sudoedit /etc/motd
Defaults!EDIT_MOTD env_delete+="SUDO_EDITOR VISUAL EDITOR"
user ALL = EDIT_MOTD
Defaults!EDIT_MOTD env_delete+="SUDO_EDITOR VISUAL EDITOR"
user ALL = EDIT_MOTD
However, we recommend upgrading to the current stable release sudo 1.9.13p3 released on March 6, 2023.
To remediate this issue, go to the Product Downloads site, and download the applicable product update/hotfix file:
| Product | Version | Type | Release Date |
| Threat Intelligence Exchange | 4.0.0 HF 2 | Hotfix | 11 April, 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:
- 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 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.
What are the CVSS scoring metrics?
CVE-2023-22809: sudo: arbitrary file write with privileges.
| Base Score | 7.8 |
| Attack Vector (AV) | Local (L) |
| Attack Complexity (AC) | Low (L) |
| Privileges Required (PR) | Low (L) |
| User Interaction (UI) | None (N) |
| Scope (S) | Unchanged |
| Confidentiality (C) | High (H) |
| Integrity (I) | High (H) |
| Availability (A) | High (H) |
| Temporal Score (Overall) | 7.0 |
| Exploitability (E) | Proof-of-Concept (P) |
| Remediation Level (RL) | Official Fix (O) |
| Report Confidence (RC) | Confirmed (C) |
NOTE: This CVSS version 3.1 vector, linked here, 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.
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.
