Security Bulletin - Network Security Manager/Network Security Platform/Network Threat Behavior Analysis update fixes multiple vulnerabilities (CVE-2013-4559, CVE-2015-3200, CVE-2016-2183, CVE-2020-7256, CVE-2020-7258)
Security Bulletins ID:
SB10310
Last Modified: 2022-05-04 16:52:03 Etc/GMT
Last Modified: 2022-05-04 16:52:03 Etc/GMT
Summary
First Published: March 17, 2020
Article contents:
This Security Bulletin addresses weak cipher usage between NSP and NTBA and Cross Site Scripting issues in NSM. The cipher issue is addressed by updating third-party libraries, and the Cross Site Scripting issues were our code base.
Weak Cipher Usage in NSP and NTBA Communication
Communication from NSP Sensor M-series and VM-series to NTBA now uses TLS1.2-RSA-AES128_GCM-SHA256. When updating NTBA to 9.1 Update 6, it is recommended to also upgrade all co-deployed NSP sensors (M, NS, or VM series) to maintain encrypted communication seamlessly.
If you are on a version earlier then 9.1 Update 6 for your product, you should update as shown in the table below.
Go to the Product Downloads site, and download the applicable product update file:
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 you install the available maintenance versions listed in the table above. No temporary workaround is offered.
Acknowledgments
We credit the Govt. of Taiwan for reporting the weak cipher usage.
We credit Albert Sanchez for reporting CVE-2020-7256.
We credit Adrià Alavedra Palacio for reporting CVE-2020-7258.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
Use the following instructions for Appliance-based products:
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?
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: | Information exposure (CWE-200) Improper neutralization of output by possible injection (CWE-74) Privilege escalation (CWE-264) Cross Site Scripting (XSS) (CWE-79) |
| CVE ID: | Third party: CVE-2013-4559, CVE-2015-3200, CVE-2016-2183 McAfee code: CVE-2020-7256, CVE-2020-7258 |
| Highest Severity Rating: | High |
| CVSS v3 Base/Temporal Scores: | CVE-2015-3200: 7.5 / 3.6 CVE-2016-2183: 7.5 / 3.6 CVE-2020-7256: 4.8 / 4.6 CVE-2020-7258: 4.8 / 4.6 |
| Recommendations: | Update to:
|
| 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
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
This Security Bulletin addresses weak cipher usage between NSP and NTBA and Cross Site Scripting issues in NSM. The cipher issue is addressed by updating third-party libraries, and the Cross Site Scripting issues were our code base.
Weak Cipher Usage in NSP and NTBA Communication
Communication from NSP Sensor M-series and VM-series to NTBA now uses TLS1.2-RSA-AES128_GCM-SHA256. When updating NTBA to 9.1 Update 6, it is recommended to also upgrade all co-deployed NSP sensors (M, NS, or VM series) to maintain encrypted communication seamlessly.
- CVE-2013-4559
lighttpd before 1.4.33 does not check the return value of the (1) setuid, (2) setgid, or (3) setgroups functions, which might cause lighttpd to run as root if it is restarted and allows remote attackers to gain privileges, as demonstrated by multiple calls to the clone function that cause setuid to fail when the user process limit is reached.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4559
- CVE-2015-3200
mod_auth in lighttpd before 1.4.36 allows remote attackers to inject arbitrary log entries via a basic HTTP authentication string without a colon character, as demonstrated by a string containing a NULL and new line character.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3200
- CVE-2016-2183
The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, also known as a "Sweet32" attack.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183
- CVE-2020-7256
Cross Site Scripting (XSS) vulnerability in Network Security Manager (NSM) prior to 9.1 Update 6 allows an authenticated administrator to embed an XSS in the administrator interface via a specially crafted custom rule containing HTML.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7256
https://nvd.nist.gov/vuln/detail/CVE-2020-7256
- CVE-2020-7258
Cross Site Scripting (XSS) vulnerability in Network Security Manager (NSM) prior to 9.1 Update 6 allows an authenticated administrator to embed an XSS in the administrator interface via a specially crafted custom rule containing HTML.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7258
https://nvd.nist.gov/vuln/detail/CVE-2020-7258
If you are on a version earlier then 9.1 Update 6 for your product, you should update as shown in the table below.
Go to the Product Downloads site, and download the applicable product update file:
| Product | Version | Type | Release Date |
| NSM | 9.1 Update 6 (9.1.7.80) | Update | March 17, 2020 |
| NSP Sensor M-series | 9.1 Update 6 (9.1.3.16) | Update | March 17, 2020 |
| NSP Sensor VM-series | 9.1 Update 6 (9.1.7.25) | Update | March 17, 2020 |
| NSP Sensor NS-series | 9.1 Update 6 (9.1.5.80) | Update | March 17, 2020 |
| NTBA | 9.1 Update 6 (9.1.3.63) | Update | March 17, 2020 |
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 you install the available maintenance versions listed in the table above. No temporary workaround is offered.
Acknowledgments
We credit the Govt. of Taiwan for reporting the weak cipher usage.
We credit Albert Sanchez for reporting CVE-2020-7256.
We credit Adrià Alavedra Palacio for reporting CVE-2020-7258.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
- Right-click on the McAfee tray shield icon on the Windows taskbar.
- Select Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. The product version displays.
Use the following instructions for Appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version displays.
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-2020-7256 - Cross Site Scripting vulnerability in NSM
Base Score 4.8 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) High (H) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 4.6 Exploitability (E) High (H) 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-calculator?vector=AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:H/RL:O/RC:C&version=3.1
- CVE-2020-7258 - Cross Site Scripting vulnerability in NSM
Base Score 4.8 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) High (H) User Interaction (UI) Required (R) Scope (S) Changed (C) Confidentiality (C) Low (L) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 4.6 Exploitability (E) High (H) 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-calculator?vector=AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:H/RL:O/RC:C&version=3.1
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.
