Cross site scripting vulnerability in McAfee Network Security Management (NSM) Prior to 9.1

Overview :
Cross site scripting vulnerability in McAfee Network Security Management (NSM) Prior to 9.1 update 6 Mar 2020 Update allows attackers to unspecified impact via unspecified vectors.

McAfee 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:  3/17/2020

 

Vulnerability Details :       

CVE-2020-7258

Vulnerability Description
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 in McAfee’s 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.

  1. 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
  2. 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
  3. 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

Cross Site Scripting in NSM

  1. CVE-2020-7256
    Cross Site Scripting (XSS) vulnerability in McAfee 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
  2. CVE-2020-7258
    Cross Site Scripting (XSS) vulnerability in McAfee 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

Remediation
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
See KB56057 for instructions on how to download McAfee products, documentation, updates, and hotfixes. Review the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions on how to install these updates.
Workaround
McAfee strongly recommends you install the available maintenance versions listed in the table above. No temporary workaround is offered.
Acknowledgments
McAfee credits the Govt. of Taiwan for reporting the weak cipher usage.
McAfee credits Albert Sanchez for reporting CVE-2020-7256.
McAfee credits Adrià Alavedra Palacio for reporting CVE-2020-7258.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable or not?
For Endpoint products:
Use the following instructions for endpoint or client-based products:

  1. Right-click on the McAfee tray shield icon on the Windows taskbar.
  2. Select Open Console.
  3. In the console, select Action Menu.
  4. In the Action Menu, select Product Details. The product version displays.

For Appliances:
Use the following instructions for Appliance-based products:

  1. Open the Administrator’s User Interface (UI).
  2. Click the About link. The product version displays.

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: http://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?

  1. 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

  2. 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

Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our external PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > 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 http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Report a Security Vulnerability.

How does McAfee respond to this and any other reported security flaws?
McAfee’s key priority is the security of our customers. If a vulnerability is found within any of McAfee’s 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 http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > 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:

  • 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 required fields. Your password and logon instructions will be emailed to you.