Security Bulletin - Endpoint Security for Windows update fixes three vulnerabilities (CVE-2019-3652, CVE-2019-3653, and CVE-2020-7251)
Security Bulletins ID:
SB10299
Last Modified: 5/4/2022
Last Modified: 5/4/2022
Summary
First Published: October 8, 2019
Article contents:
This Security Bulletin covers three vulnerabilities in ENS. To exploit these vulnerabilities, an attacker would need to gain access to the system.
The initial fix for this issue in CVE-2019-3653 doesn't prevent an older version of the ESConfig Tool from modifying the configuration for later versions. CVE-2020-7251 addresses this issue for ENS 10.6.1 and 10.7.0.
To remediate these issues, the following criteria must be met:
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 Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Acknowledgments
CVE-2019-3652: We credit Russell Wells from DRS for reporting this flaw.
CVE-2019-3653: We credit Donny Maasland from Fox-IT for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Follow the instructions below for endpoint or client-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 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?
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 | CVE-2019-3652 - Code Injection (CWE-94) CVE-2019-3653 - Improper Access Control (CWE-287) CVE-2020-7251 - Improper Access Control (CWE-287) |
| CVE ID | CVE-2019-3652 CVE-2019-3653 CVE-2020-7251 |
| Severity Rating | CVE-2019-3652: Medium CVE-2019-3653: Medium CVE-2020-7251: Medium |
| CVSS v3 Base/Temporal Scores | CVE-2019-3652: 5.0 / 4.3 CVE-2019-3653: 5.0 / 4.3 CVE-2020-7251: 5.0 / 4.3 |
| Recommendations | Install or update to one of the following Endpoint Security (ENS) versions:
|
| Security Bulletin Replacement | Update to CVE-2019-3653 for ENS 10.6.1. |
| Affected Software | ENS for Windows:
|
| 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 Security Bulletin covers three vulnerabilities in ENS. To exploit these vulnerabilities, an attacker would need to gain access to the system.
The initial fix for this issue in CVE-2019-3653 doesn't prevent an older version of the ESConfig Tool from modifying the configuration for later versions. CVE-2020-7251 addresses this issue for ENS 10.6.1 and 10.7.0.
- CVE-2019-3652 - ENS code injection in
EPSetup.exe
Code Injection vulnerability inEPSetup.exe in ENS prior to 10.6.1 October 2019 Update allows local users to get their malicious code installed by the ENS installer via code injection intoEPSetup.exe by an attacker with access to the installer.
NVD CVE-2019-3652
MITRE CVE-2019-3652
- CVE-2019-3653 - ESConfig Tool access not controlled
Improper access control vulnerability in the configuration tool in ENS prior to 10.6.1 October 2019 Update allows local users to disable security features via unauthorized use of the configuration tool.
NVD CVE-2019-3653
MITRE CVE-2019-3653
- CVE-2020-7251 - ESConfig Tool able to edit configuration for newer versions
Improper access control vulnerability in the configuration tool in ENS prior to 10.6.1 February 2020 Update allows local users to disable security features via unauthorized use of the configuration tool from older versions of ENS.
NVD CVE-2020-7251
MITRE CVE-2020-7251
To remediate these issues, the following criteria must be met:
- Customers using ENS 10.7.x should update to ENS 10.7.0 February 2020 Update.
- Customers using ENS 10.6.x should either upgrade to ENS 10.7.0 February 2020 Update or update to ENS 10.6.1 February 2020 Update.
| Product | Version | Type | Release Date | Restart Needed? |
| ENS for Windows | 10.7.0 February 2020 Update | Update | February 13, 2020 | No |
| ENS for Windows | 10.6.1 February 2020 Update | Update | February 13, 2020 | No |
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 Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Acknowledgments
CVE-2019-3652: We credit Russell Wells from DRS for reporting this flaw.
CVE-2019-3653: We credit Donny Maasland from Fox-IT for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Follow the instructions below for endpoint or client-based products:
- Right-click on the tray shield icon on the Windows taskbar.
- Click Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. 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-2019-3652 - ENS code injection in EPSetup.exe
Base Score 5.0 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) Low (L) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) Low (L) Integrity (I) Low (L) Availability (A) Low (L) Temporal Score (Overall) 4.3 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Reasonable (R)
NOTE: This CVSS version 3.0 vector is used to generate this score.
- CVE-2019-3653 - ESConfig Tool access not controlled
Base Score 5.0 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) Low (L) 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.3 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Confirmed (C)
NOTE: This CVSS version 3.0 vector is used to generate this score.
- CVE-2020-7251 - ESConfig Tool able to edit configuration for newer version
Base Score 5.0 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) Low (L) 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.3 Exploitability (E) Proof-of-Concept (P) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Reasonable (R)
NOTE: This CVSS version 3.1 vector is 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.
