Security Bulletin - ePolicy Orchestrator Cloud update fixes multiple Cross-Site Request Forgery vulnerabilities (CVE-2019-3604)
Security Bulletins ID:
SB10268
Last Modified: 2022-05-04 15:34:47 Etc/GMT
Last Modified: 2022-05-04 15:34:47 Etc/GMT
Summary
First Published: January 31, 2019
Article contents:
There were multiple Cross-Site Request Forgery issues with the legacy ePO Cloud versions.
CVE-2019-3604
Cross-Site Request Forgery (CSRF) vulnerability in ePO (legacy) Cloud allows unauthenticated users to perform unintended ePO actions using an authenticated user's session via unspecified vectors.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3604
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3604
Affected Component:
The latest patch has been deployed to ePO Cloud.
Acknowledgments
We credit Ankur Parsai from PricewaterhouseCoopers for reporting this vulnerability.
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.
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-2019-3604: Multiple Cross-Site Request Forgery issues in ePO Cloud
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N/E:F/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: | Cross-Site Request Forgery (CSRF) (CWE-352) |
CVE ID: | CVE-2019-3604 |
Severity Rating: | Medium |
CVSS v3 Base/Temporal Scores: | 4.8 / 4.5 |
Recommendations: | None |
Security Bulletin Replacement: | None |
Affected Software: | Legacy ePolicy Orchestrator (ePO) Cloud |
Location of updated software: | None, cloud offering only |
Article contents:
- Vulnerability Description
- Remediation
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
There were multiple Cross-Site Request Forgery issues with the legacy ePO Cloud versions.
CVE-2019-3604
Cross-Site Request Forgery (CSRF) vulnerability in ePO (legacy) Cloud allows unauthenticated users to perform unintended ePO actions using an authenticated user's session via unspecified vectors.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3604
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3604
Affected Component:
- User Management service
The latest patch has been deployed to ePO Cloud.
Acknowledgments
We credit Ankur Parsai from PricewaterhouseCoopers for reporting this vulnerability.
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.
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-2019-3604: Multiple Cross-Site Request Forgery issues in ePO Cloud
Base Score | 4.8 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | High (H) |
Privileges Required (PR) | High (H) |
User Interaction (UI) | Required (R) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | High (H) |
Integrity (I) | Low (L) |
Availability (A) | None (N) |
Temporal Score (Overall) | 4.5 |
Exploitability (E) | Functional exploit exists (F) |
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://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N/E:F/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.