Security Bulletin - ePolicy Orchestrator update fixes Tomcat vulnerability (CVE-2018-11784)
Security Bulletins ID:
SB10257
Last Modified: 2022-05-04 15:31:42 Etc/GMT
Last Modified: 2022-05-04 15:31:42 Etc/GMT
Summary
First Published: November 27, 2018
Article contents:
ePO runs on Apache Tomcat and according to the CVE listed below, the Tomcat update consumed by ePO is possibly vulnerable to invalidated redirects to any URI of an attacker's choice.
This ePO update resolves the following issue:
CVE-2018-11784
When the default servlet returned a redirect to a directory (for example, redirecting to /foo/ when the user requested /foo) a specially crafted URL could be used to cause the redirect to be generated to any URI of the attacker's choice.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11784
https://nvd.nist.gov/vuln/detail/CVE-2018-11784
Affected Component:
To remediate this issue:
*NOTE: We will use commercially reasonable efforts to release an update by the planned date, but plans might change.
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Product Specific Notes
ePO 5.1.x reached End of Life on December 31, 2017. We recommend that all customers upgrade to ePO 5.9.x or 5.10.x.
Workaround
None. Installing the latest ePO hotfix or update specified in the Remediation table is strongly encouraged.
Acknowledgments
None.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For ePO:
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about how to check the version, see: KB52634.
What is CVSS?
CVSS, or Common Vulnerability Scoring System, 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 at: http://www.first.org/cvss/.
When calculating CVSS scores, we've 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 do not 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-2018-11784: ePO and Apache Tomcat
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C
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.
Impact of Vulnerability: | Invalidated Redirects and Forwards |
CVE ID: | CVE-2018-11784 |
Severity Rating: | Medium |
CVSS v3 Base/Temporal Scores: | 5.3 / 4.6 |
Recommendations: | Apply the standalone hotfix or update. |
Security Bulletin Replacement: | None |
Affected Software: |
|
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
- Workaround
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
ePO runs on Apache Tomcat and according to the CVE listed below, the Tomcat update consumed by ePO is possibly vulnerable to invalidated redirects to any URI of an attacker's choice.
This ePO update resolves the following issue:
CVE-2018-11784
When the default servlet returned a redirect to a directory (for example, redirecting to /foo/ when the user requested /foo) a specially crafted URL could be used to cause the redirect to be generated to any URI of the attacker's choice.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11784
https://nvd.nist.gov/vuln/detail/CVE-2018-11784
Affected Component:
- ePO web core services
To remediate this issue:
- Users of ePO 5.3.2 or earlier are recommended to upgrade to ePO 5.3.3, 5.9.1, or 5.10 and apply the fix for the version you upgraded to. See the table below for the relevant fix.
- Users of ePO 5.9.0 are recommended to upgrade to ePO 5.9.1 or 5.10 and apply the fix for the version you upgraded to. See the table below for the relevant fix.
- Users of ePO 5.3.3 are recommended to apply EPO533HF1257674r.zip.
- Users of ePO 5.9.1 are recommended to apply EPO591HF1260432r.zip.
- Users of ePO 5.10.0 are recommended to apply ePO_5.10.0_Update_2.zip.
Product | Type | File Name | Release Date |
ePO 5.10.0 Update 2 | Update | ePO_5.10.0_Update_2.zip | December 11, 2018 |
ePO 5.9.1 | Hotfix | EPO591HF1260432r.zip | November 27, 2018 |
ePO 5.3.3 | Hotfix | EPO533HF1257674r.zip | November 27, 2018 |
*NOTE: We will use commercially reasonable efforts to release an update by the planned date, but plans might change.
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Product Specific Notes
ePO 5.1.x reached End of Life on December 31, 2017. We recommend that all customers upgrade to ePO 5.9.x or 5.10.x.
Workaround
None. Installing the latest ePO hotfix or update specified in the Remediation table is strongly encouraged.
Acknowledgments
None.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For ePO:
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about how to check the version, see: KB52634.
What is CVSS?
CVSS, or Common Vulnerability Scoring System, 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 at: http://www.first.org/cvss/.
When calculating CVSS scores, we've 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 do not 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-2018-11784: ePO and Apache Tomcat
Base Score | 5.3 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | Low (L) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | None (N) |
Integrity (I) | Low (L) |
Availability (A) | None (N) |
Temporal Score (Overall) | 4.6 |
Exploitability (E) | Unproven (U) |
Remediation Level (RL) | Official Fix (O) |
Report Confidence (RC) | Confirmed (C) |
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C
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.
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.
Affected Products
Languages:
This article is available in the following languages: