Security Bulletin – On-Prem ePO SP1 UP1 addresses CVE-2023-3946 and Multiple Third-Party Vulnerabilities
Security Bulletins ID:
SB10402
Last Modified: 2023-08-08 04:47:03 Etc/GMT
Last Modified: 2023-08-08 04:47:03 Etc/GMT
Summary
First Published: July 25, 2023
Article contents:
This release addresses one ePO code vulnerability and three third-party library updates that ePO uses. The third-party libraries are listed, as we've received several queries from customers asking about our status. Third-party libraries are updated regularly and only called out in Security Bulletins if we receive a significant number of queries.
ePO code vulnerabilities:
The third-party libraries updated in this release are as follows:
To remediate this issue, customers using ePO 5.10 should update to ePO 5.10 SP1 Update 1.
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 Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Acknowledgments
Trellix credits Ben Leonard-Lagarde and Freddie Sibley-Calder (Modux) for responsibly reporting CVE-2023-3946.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For Endpoint Security (ENS) on Windows:
Follow the instructions below for endpoint or client-based products:
Use the following instructions for endpoint or client-based products:
Use the following instructions for server-based products:
Follow the instructions below for appliance-based products:
Follow the instructions below:
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-2023-3946: Reflected XSS in ePO server:
NOTE: This CVSS version 3.1 vector was used to generate this score.
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
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 |
| ePolicy Orchestrator (ePO) | ePO 5.10.0 SP1 and earlier | CVE-2023-3946 | CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | Medium | 5.4/4.9 |
| See the |
|||||
| Java CVEs | See the Java Security Advisory link below | ||||
| Tomcat CVEs | See the Tomcat Security Advisory link below | ||||
| Recommendations | Install or update to the latest versions listed below | ||||
| 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
This release addresses one ePO code vulnerability and three third-party library updates that ePO uses. The third-party libraries are listed, as we've received several queries from customers asking about our status. Third-party libraries are updated regularly and only called out in Security Bulletins if we receive a significant number of queries.
ePO code vulnerabilities:
CVE-2023-3946
A reflected cross-site scripting (XSS) vulnerability in ePO prior to the ePO 5.10 SP1 Update 1 allows a remote unauthenticated attacker to potentially obtain access to an ePO administrator's session by convincing the authenticated ePO administrator to click on a carefully crafted link. This would lead to limited access to sensitive information and limited ability to alter some information in ePO,
MITRE CVE-2023-3946
MITRE CVE-2023-3946
The third-party libraries updated in this release are as follows:
OpenSSL has been updated to1.0.2zh-fips .
OpenSSL Security Advisory
- JRE has been updated to the July 2023 update 1.8.0_371.
Details on the CVEs published by Java are in the JRE Security Advisory.
- Tomcat has been updated to the July 2023 update 9.0.76.
Details on the CVEs published by Tomcat are in the Tomcat Security Advisory.
To remediate this issue, customers using ePO 5.10 should update to ePO 5.10 SP1 Update 1.
Go to the Product Downloads site and download the applicable product update/hotfix file:
| Product | Version | Type | Release Date |
| ePO on-Prem | SP1 UP1 | Service Pack | July 25, 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 Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Acknowledgments
Trellix credits Ben Leonard-Lagarde and Freddie Sibley-Calder (Modux) for responsibly reporting CVE-2023-3946.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable or not?
For Endpoint Security (ENS) on Windows:
Follow the instructions below 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's 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.
Follow the instructions below for appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version displays.
Follow the instructions below:
- 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-2023-3946: Reflected XSS in ePO server:
| Base Score | 5.4 |
| Attack Vector (AV) | Network (N) |
| Attack Complexity (AC) | Low (L) |
| Privileges Required (PR) | None (N) |
| User Interaction (UI) | Required (R) |
| Scope (S) | Unchanged (U) |
| Confidentiality (C) | Low (L) |
| Integrity (I) | Low (L) |
| Availability (A) | None (N) |
| Temporal Score (Overall) | 4.9 |
| 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.
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
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.
