Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2020.3547
ePolicy Orchestrator update addresses multiple vulnerabilities
15 October 2020
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: McAfee ePolicy Orchestrator
Publisher: McAfee
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Virtualisation
Impact/Access: Execute Arbitrary Code/Commands -- Remote with User Interaction
Modify Arbitrary Files -- Remote/Unauthenticated
Denial of Service -- Remote/Unauthenticated
Cross-site Scripting -- Remote with User Interaction
Read-only Data Access -- Remote/Unauthenticated
Unauthorised Access -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2020-14621 CVE-2020-14581 CVE-2020-14579
CVE-2020-14578 CVE-2020-14573 CVE-2020-13935
CVE-2020-9484 CVE-2020-7318 CVE-2020-7317
CVE-2020-2773 CVE-2020-2764 CVE-2020-2757
CVE-2020-2756 CVE-2020-2755 CVE-2020-2754
Reference: ASB-2020.0076
ESB-2020.3496
ESB-2020.3232
ESB-2020.3015
ESB-2020.2807
ESB-2020.2677
ESB-2020.2670
ESB-2020.2545
Original Bulletin:
https://kc.mcafee.com/corporate/index?page=content&id=SB10332
- --------------------------BEGIN INCLUDED TEXT--------------------
McAfee Security Bulletin - ePolicy Orchestrator update addresses multiple
vulnerabilities (CVE-2020-7317, CVE-2020-7318, CVE-2020-13935, CVE-2020-9484,
CVE-2020-14621, CVE-2020-14573, CVE-2020-14578, CVE-2020-14579, CVE-2020-14581,
CVE-2020-2754, CVE-2020-2755, CVE-2020-2756, CVE-2020-2757, CVE-2020-2764,
CVE-2020-2773)
Security Bulletins ID : SB10332
Last Modified : 10/13/2020
Summary
First Published: October 13, 2020
+----------------+--------------+------------------------+--------+-----------+
| | | | |CVSS v3.1 |
|Product: |CVE ID: |Impact of |Severity|Base/ |
| | |Vulnerabilities: |Ratings:|Temporal |
| | | | |Scores: |
+----------------+--------------+------------------------+--------+-----------+
| |CVE-2020-7317 |Improper Neutralization |Medium |4.6 / 4.2 |
| | |of Input (CWE-79) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-7318 |Improper Neutralization |Medium |4.6 / 4.2 |
| | |of Input (CWE-79) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-13935|Denial of Service |High |7.5 |
| | |(CWE-730) | | |
| +--------------+------------------------+--------+-----------+
| | |Improper Control of | | |
| |CVE-2020-9484 |Generation of Code |High |7.0 |
| | |(CWE-94) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-14621|Incorrect Authorization |Medium |5.3 |
| | |(CWE-863) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-14573|Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-14578|Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
|ePolicy +--------------+------------------------+--------+-----------+
|Orchestrator |CVE-2020-14579|Improper Input |Low |3.7 |
|(ePO) | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-14581|Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-2754 |Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-2755 |Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-2756 |Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-2757 |Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-2764 |Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
| +--------------+------------------------+--------+-----------+
| |CVE-2020-2773 |Improper Input |Low |3.7 |
| | |Validation (CWE-20) | | |
+----------------+--------------+------------------------+--------+-----------+
|Highest rating: |High |
+----------------+------------------------------------------------------------+
|Impacted |ePO 5.9.x, ePO 5.10.0 prior to ePO 5.10.0 Update 9 |
|versions: | |
+----------------+------------------------------------------------------------+
|Recommendations:|Install or update to ePO 5.10.0 Update 9 |
+----------------+------------------------------------------------------------+
|Security | |
|Bulletin |None |
|Replacement: | |
+----------------+------------------------------------------------------------+
|Location of | |
|updated |http://www.mcafee.com/us/downloads/downloads.aspx |
|software: | |
+----------------+------------------------------------------------------------+
To receive email notification when this Security Bulletin is updated, click
Subscribe on the right side of the page. You must be logged on to subscribe.
Article contents:
o Vulnerability Description
o Remediation
o Acknowledgments
o Frequently Asked Questions (FAQs)
o Resources
o Disclaimer
Vulnerability Description
This Security Bulletin contains details of vulnerabilities discovered in the
ePO code base as well as in third-party libraries. They range in severity from
Low to High and McAfee recommends you update to the latest ePO version.
Third-party libraries:
Tomcat
1. CVE-2020-13935
The payload length in a WebSocket frame was not correctly validated in
Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56
and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite
loop. Multiple requests with invalid payload lengths could lead to a denial
of service.
2. CVE-2020-9484
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to
9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to
control the contents and name of a file on the server; and b) the server is
configured to use the PersistenceManager with a FileStore; and c) the
PersistenceManager is configured with sessionAttributeValueClassNameFilter=
"null" (the default unless a SecurityManager is used) or a sufficiently lax
filter to allow the attacker provided object to be deserialized; and d) the
attacker knows the relative file path from the storage location used by
FileStore to the file the attacker has control over; then, using a
specifically crafted request, the attacker will be able to trigger remote
code execution via deserialization of the file under their control. Note
that all of conditions a) to d) must be true for the attack to succeed.
Java
3. CVE-2020-14573
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE. Successful attacks of this
vulnerability can result in unauthorized update, insert or delete access to
some of Java SE accessible data.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
4. CVE-2020-14578
vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
5. CVE-2020-14581
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized read access to a
subset of Java SE, Java SE Embedded accessible data.
NOTE: Applies to client and server deployment of Java.
6. CVE-2020-14621
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized update, insert or
delete access to some of Java SE, Java SE Embedded accessible data.
7. CVE-2020-14579
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
8. CVE-2020-2754
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
9. CVE-2020-2755
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
10. CVE-2020-2756
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
11. CVE-2020-2757
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
12. CVE-2020-2764
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE. Successful attacks of this
vulnerability can result in unauthorized read access to a subset of Java SE
accessible data.
13. CVE-2020-2773
The vulnerability allows unauthenticated attacker with network access via
multiple protocols to compromise Java SE, Java SE Embedded. Successful
attacks of this vulnerability can result in unauthorized ability to cause a
partial denial of service (partial DOS) of Java SE, Java SE Embedded.
NOTE: Applies to client and server deployment of Java. This vulnerability
can be exploited through sandboxed Java Web Start applications and
sandboxed Java applets.
ePO code base
These issues only affect the on premise version of ePO.
14. CVE-2020-7317
Cross-Site Scripting vulnerability in McAfee ePolicy Orchestrator (ePO)
prior to 5.10.9 Update 9 allows administrators to inject arbitrary web
script or HTML via parameter values for "syncPointList" not being correctly
sanitized.
15. CVE-2020-7318
Cross-Site Scripting vulnerability in McAfee ePolicy Orchestrator (ePO)
prior to 5.10.9 Update 9 allows administrators to inject arbitrary web
script or HTML via multiple parameters where the administrator's entries
were not correctly sanitized.
Remediation
To remediate this issue:
o Customers using ePO 5.10 should update to ePO 5.10.0 Update 9.
o Customers using ePO 5.9.1 and earlier:
Should upgrade to ePO 5.10.0 Update 9 to receive fixes for the Java,
Tomcat, and XSS issues.
Wait for the ePO 5.9.1 Hotfix to be released to receive fixes for only
the Java and Tomcat issues.
Go to the Product Downloads site , and download the applicable product update/
hotfix files:
+-------+---------------+------+----------------+
|Product|Version |Type |Release Date |
+-------+---------------+------+----------------+
|ePO |5.10.0 Update 9|Update|October 13, 2020|
+-------+---------------+------+----------------+
|ePO |5.9.1 |Hotfix|To be confirmed |
+-------+---------------+------+----------------+
Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation,
updates, and hotfixes. Review the Release Notes and the Installation Guide for
instructions on how to install these updates. All documentation is available at
https://docs.mcafee.com .
Acknowledgments
CWE-2020-7317: McAfee acknowledges Frank Plattel from Radically Open Security
for responsibly disclosing this.
CWE-2020-7318: McAfee acknowledges Mikhail Klyuchnikov from Positive
Technologies for responsibly disclosing this.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable or not
For ePO/server products:
Use the following instructions for server-based products:
o Check the version and build of ePO that is installed. For information on
how to check the version, see KB52634 .
o Create a query in ePO for the product version of the product installed
within your organization.
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: https://www.first.org/cvss/ .
When calculating CVSS scores, McAfee has 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
14. CVE-2020-7317: ePO Cross-Site Scripting vulnerability
+------------------------+-------------------------+
|Base Score |4.6 |
+------------------------+-------------------------+
|Attack Vector (AV) |Adjacent Nework (A) |
+------------------------+-------------------------+
|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.2 |
+------------------------+-------------------------+
|Exploitability (E) |Proof of concept code (P)|
+------------------------+-------------------------+
|Remediation Level (RL) |Official Fix (O) |
+------------------------+-------------------------+
|Report Confidence (RC) |Confirmed (C) |
+------------------------+-------------------------+
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculatorvector=AV:A/AC:L/PR:N/
UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C&version=3.1
15. CVE-2020-7318: ePO Cross-Site Scripting vulnerability
+------------------------+-------------------------+
|Base Score |4.6 |
+------------------------+-------------------------+
|Attack Vector (AV) |Adjacent Network (A) |
+------------------------+-------------------------+
|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.2 |
+------------------------+-------------------------+
|Exploitability (E) |Proof of concept code (P)|
+------------------------+-------------------------+
|Remediation Level (RL) |Official Fix (O) |
+------------------------+-------------------------+
|Report Confidence (RC) |Confirmed (C) |
+------------------------+-------------------------+
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculatorvector=AV:A/AC:L/PR:N/
UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C&version=3.1
Where can I find a list of all Security Bulletins
All Security Bulletins are published on our external PSIRT website at https://
www.mcafee.com/us/threat-center/product-security-bulletins.aspx . To see
Security Bulletins for McAfee Enterprise products on this website click
Enterprise Security Bulletins . 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 McAfee
If you have information about a security issue or vulnerability with a McAfee
product, visit the McAfee PSIRT website for instructions at https://
www.mcafee.com/us/threat-center/product-security-bulletins.aspx . To report an
issue, click Report a Security Vulnerability .
How does McAfee 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 McAfee 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.
McAfee only publishes 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.
View our PSIRT policy on the McAfee PSIRT website at https://www.mcafee.com/us/
threat-center/product-security-bulletins.aspx by clicking About PSIRT .
Resources
To contact Technical Support, log on to the ServicePortal and go to the Create
a Service Request page at https://support.mcafee.com/ServicePortal/faces/
serviceRequests/createSR :
o If you are a registered user, type your User ID and Password, and then
click Log In .
o If you are not a registered user, click Register and complete the required
fields. Your password and logon instructions will be emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without
warranty of any kind. McAfee disclaims all warranties, either express or
implied, including the warranties of merchantability and fitness for a
particular purpose. In no event shall McAfee or its suppliers be liable for any
damages whatsoever including direct, indirect, incidental, consequential, loss
of business profits or special damages, even if McAfee or its suppliers have
been advised of the possibility of such damages. Some states do not 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 should not 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 are not 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 remains at
our sole discretion and may be changed or canceled at any time
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBX4ejZ+NLKJtyKPYoAQg+kA//bqrfv8Cg42c9TN/LdJo6QZ4LMZmkfv35
RwwRbtewQK1kQn842Q/FEDJnMNR/UZ1nAcWwZ3ny2VGxms5twyn2PiRQBfiCvx/U
9MQX3c9dZ2iY0rckgErpaH/FxiJ4LsZbWQpucMkJIdnAC56822O3uLdNEqTkY6e7
47RPartXmILstw+Q1IKoPKeFdpjiAfPwzsrZIr9A2fI8vvOfZCM3vtfIV6UPcNEC
+K38cCmXSzRObVmcQO0iORV+czUjStVSPmQYrrEydrbjt+dnxFsDxdQ2bjZMlAb0
BQNg16RucZgyqDaEpzWSWOCeMTkvOx5529Gj7WFA3mTU0vHTY/hz3EO/3oAlILXR
IZf0cQPxPKy8axkjzF7SR0RRd+npO8LJyDRPT6knglq9FskpKeRlvpMwtsE1IMU/
qkBOITUblmhq7GZWCpPuwB4wSZvnpdBHMKqgbzF3eccnUK+v2/Nd00GG5HSiqfNb
iMfw4ag5f5iIOz9ScbN+4k6KTg/cYP3piBhHpaaDFCiYtXF36FEcHRkRW0XHpG2n
0auLnVIfl3TF8jSuPRLZzN9PEycwXf/wlvO+P1brzpzIETqyZ5L2G/aiDpwbgh65
6JZU8tqTTNfW3kuDNCLYVZIdB0pLwy357hn+iMIrR1dTg455b1jqLlb1qe7PtoUb
/THRGszjaO4=
=/jgj
-----END PGP SIGNATURE-----