Security Bulletin – ePolicy Orchestrator update fixes a TLS issue between ePolicy Orchestrator Agent Handler and SQL Server (CVE-2019-3619)
Security Bulletins ID:
SB10286
Last Modified: 5/4/2022
Last Modified: 5/4/2022
Summary
First Published: July 2, 2019
Article contents:
ePO offers the ability to configure the communication between the McAfee Agent Handler and the SQL Server to be plain text or encrypted over TLS. The Agent Handler was only honoring some of the TLS options, and was incorrectly reverting to plain text communication for the others.
CVE-2019-3619:
Information Disclosure vulnerability in the Agent Handler in ePolicy Orchestrator (ePO) 5.9.x and 5.10.0 before 5.10.0 Update 4 allows a remote unauthenticated attacker to view sensitive information in plain text via sniffing the traffic between the Agent Handler and the SQL Server.
Remediation
We strongly recommend that you install the latest update or hotfix for your version of ePO.
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.
Workaround
We strongly recommend that you install the available update/hotfix. If you cannot, consider forcing encryption while connecting to the database as a temporary workaround.
Workaround 1:
To enable encryption on the SQL Server:
NOTE: This workaround requires ePO to be configured to use TLS when connecting to the SQL Server.
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-3619: ePO Agent Handler not enforcing TLS
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:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/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: | Insufficient Transport Layer Protection (CWE-818, OWASP 2010:A9) |
CVE ID: | CVE-2019-3619 |
Severity Rating: | Medium |
CVSS v3 Base/Temporal Scores: | 6.8 / 6.3 |
Recommendations: | Install one of the following ePolicy Orchestrator (ePO) versions:
|
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
- Workaround
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
ePO offers the ability to configure the communication between the McAfee Agent Handler and the SQL Server to be plain text or encrypted over TLS. The Agent Handler was only honoring some of the TLS options, and was incorrectly reverting to plain text communication for the others.
CVE-2019-3619:
Information Disclosure vulnerability in the Agent Handler in ePolicy Orchestrator (ePO) 5.9.x and 5.10.0 before 5.10.0 Update 4 allows a remote unauthenticated attacker to view sensitive information in plain text via sniffing the traffic between the Agent Handler and the SQL Server.
Remediation
We strongly recommend that you install the latest update or hotfix for your version of ePO.
- Users of ePO 5.10.0 – Update to 5.10.0 Update 4.
- Users of ePO 5.9.1 – Apply HF1267793, or upgrade to ePO 5.10.0 Update 4.
- Users of ePO 5.9.0 – Upgrade to ePO 5.9.1 and apply HF1267793 or upgrade to ePO 5.10.0 Update 4.
Product | Version | Type | File Name | Release Date |
ePO | 5.10.0 | Update | ePO 5.10.0 Update 4 | July 2, 2019 |
ePO | 5.9.1 | Hotfix | EPO591HF1267793.zip | July 4, 2019 |
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.
Workaround
We strongly recommend that you install the available update/hotfix. If you cannot, consider forcing encryption while connecting to the database as a temporary workaround.
Workaround 1:
To enable encryption on the SQL Server:
NOTE: This workaround requires ePO to be configured to use TLS when connecting to the SQL Server.
- In SQL Server Configuration Manager, expand SQL Server Network Configuration, right-click Protocols for
, and then select Properties. - On the Flags tab, click Yes in the Force Encryption box, and then click OK to close the dialog box.
- Restart the SQL Server service.
- Follow KB84628 to make sure that the SQL Server certificate is trusted.
- Log on to the ePO console as Administrator.
- Navigate to: https://<ePO_Hostname_or_IP>:<port>/core/config
- Make sure that Always use SSL and require a trusted server certificate is selected for SSL communication with the database server.
- Make sure that Test Connection is successful and Apply the changes.
- Restart the ePO services.
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-3619: ePO Agent Handler not enforcing TLS
Base Score | 6.8 |
Attack Vector (AV) | Adjacent Network (A) |
Attack Complexity (AC) | Low (L) |
Privileges Required (PR) | High (H) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | High (H) |
Integrity (I) | High (H) |
Availability (A) | High (H) |
Temporal Score (Overall) | 6.3 |
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:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/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.