Trellix IPS Manger update fixes an XXE Injection vulnerability (CVE-2022-3340)
Security Bulletins ID:
SB10388
Last Modified: 2022-11-03 15:47:02 Etc/GMT
Last Modified: 2022-11-03 15:47:02 Etc/GMT
Summary
First Published: November 3, 2022
NOTE: Network Security Manager was rebranded to Trellix Intrusion Prevention System (IPS) Manager in version 10.1 Update 10.
Article contents:
The administrative user interface of Trellix IPS Manager did not correctly sanitize the user imported configuration XML file. An authenticated administrator attacker in the Manager GUI could use a carefully constructed XML configuration file to execute an attack to compromise the underlying server. As a partial mitigation, we recommend that the Trellix IPS Manager GUI should be on a restricted network and not exposed to the internet. Importing XML files functionality is provided for ease of configuring new IPS Managers based on existing IPS Managers. Through this import, an attacker might have:
CVE-2022-3340
XML External Entity (XXE) vulnerability in Trellix IPS Manager prior to 10.1 M8 allows a remote authenticated administrator to perform XXE attack in the administrator interface part of the interface, which allows a saved XML configuration file to be imported.
NIST CVE-2022-3340
MITRE CVE-2022-3340
Remediation
To remediate this issue, update Trellix IPS Manager to 10.1 M10.
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 Thuy Nguyen for responsibly reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For Appliances:
Use the following instructions for Appliance-based products:
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?
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.
NOTE: Network Security Manager was rebranded to Trellix Intrusion Prevention System (IPS) Manager in version 10.1 Update 10.
| Product: | Impacted Versions: | CVE ID: | Impact of Vulnerabilities: | Severity Ratings: | CVSS v3.1 Base/Temporal Scores: |
| Trellix IPS Manager | Prior to 10.1 Minor release M10 | CVE-2022-3340 | Improper Restriction of XML External Entity Reference (CWE-611) | Medium | 5.9/5.7 |
| Recommendations: | Install or update to Trellix IPS Manager 10.1 M10. | ||||
| 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 administrative user interface of Trellix IPS Manager did not correctly sanitize the user imported configuration XML file. An authenticated administrator attacker in the Manager GUI could use a carefully constructed XML configuration file to execute an attack to compromise the underlying server. As a partial mitigation, we recommend that the Trellix IPS Manager GUI should be on a restricted network and not exposed to the internet. Importing XML files functionality is provided for ease of configuring new IPS Managers based on existing IPS Managers. Through this import, an attacker might have:
- Gained access to read some of the configuration.
- Not gained access to the database of events.
- Changed some configuration with the potential to temporarily disable some of the services.
- Performed a Server side Request Forgery (SSRF) within the network the Manager is installed on.
CVE-2022-3340
XML External Entity (XXE) vulnerability in Trellix IPS Manager prior to 10.1 M8 allows a remote authenticated administrator to perform XXE attack in the administrator interface part of the interface, which allows a saved XML configuration file to be imported.
NIST CVE-2022-3340
MITRE CVE-2022-3340
Remediation
To remediate this issue, update Trellix IPS Manager to 10.1 M10.
Go to the Product Downloads site, and download the applicable product update/hotfix file:
| Product | Version | Type | Release Date |
| Trellix IPS Manager | 10.1 Minor 10
|
Update | October 27, 2022 KB92105 - Network Security Platform 10.1.x Known Issues |
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 Thuy Nguyen for responsibly reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
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.
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-2022-3340: McAfee Network Security Manager vulnerable to XSS
Base Score 5.9 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) Low (L) Integrity (I) Low (L) Availability (A) Low (L) Temporal Score (Overall) x.x Exploitability (E) High (H) 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.
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.
