F5 Networks BIG-IP Vulnerabilities

By

On July 3, 2020, F5 Networks released a notification of two vulnerabilities to the Traffic Management User Interface (TMUI) of BIG-IP network devices.  CVE-2020-5902 is a vulnerability that can result in a full device takeover via remote code execution (RCE), and CVE-2020-5903 which is a cross-site scripting (XSS) vulnerability that could also lead to RCE if the logged-in user is an administrator.

Potential Impact

The successful exploitation of CVE-2020-5902 could result in the full administrative takeover of a device without the need for authentication.  This would allow a remote attacker to intercept information, delete files, create files, execute arbitrary system commands, disable services — any action an administrator can perform.  This issue only affects the control plane (data plane is not affected).

Exploiting CVE-2020-5903, the XSS vulnerability, could allow similar results, however this vulnerability is exploited in the context of the logged in user’s permissions level.  In the event this was exploited with an administrator account currently logged in, the results could be the same as the CVE-2020-5902.

These vulnerabilities both have higher CVSSv3 scores, CVE-2020-5902 receiving the rare 10 out of 10, and 7.5 for CVE-2020-5903. Due to the existence of active attacks, proof-of-concept code, and the ease of exploitation for the RCE vulnerability, deepwatch recommends patching as soon as possible after thorough testing (prior to deployment in production).

Managing and Mitigating Risk

F5 Networks recommends updating to fully mitigate these vulnerabilities.  If you are a deepwatch VM customer, deepwatch can locate devices that have potential to have this vulnerability.  For CVE-2020-5902, the following temporary mitigations can be utilized for all network interfaces (including management interfaces) as well as Self IPs.

All network interfaces
  1. Log in to the TMOSH shell (tmsh) by entering the following command:
    tmsh
  2. Edit the httpd properties by entering the following command:
    edit /sys httpd all-properties
  3. locate the include section and add the following:
    include ‘
    <LocationMatch “.*\.\.;.*”>
    Redirect 404 /
    </LocationMatch>
  4. Write and save the changes to the configuration file by entering the following commands:
    Esc
    :wq!
  5. Save the configuration by entering the following command:
    save /sys config
  6. Restart the httpd service by entering the following command:
    restart sys service httpd
Self IPs

NOTE: this fix prevents all access to the TMUI/Configuration utility via the Self IP.  These changes may also impact other services.

Block all access to the TMUI of your BIG-IP system via Self IPs. To do so, you can change the Port Lockdown setting to Allow None for each Self IP in the system. If you must open any ports, you should use Allow Custom, taking care to disallow access to TMUI. By default, TMUI listens on TCP port 443; however, beginning in BIG-IP 13.0.0, Single-NIC BIG-IP VE deployments use TCP port 8443. Alternatively, a custom port may be configured.

Management interface

To mitigate this vulnerability for affected F5 products, you should only permit management access to F5 products over a secure network. For CVE-2020-5903, you should permit management access to F5 products only over a secure network, and limit shell access to only trusted users.

Affected versions

This vulnerability is specific to BIG-IP products (LTM, AAM, AFM, Analytics,APM, ASM, DNS, FPS, GTM, Link Controller, PEM).  Versions affected include the following:

Branch:
  • 15.x (<=15.1.0.4 vulnerable)
  • 14.x (<=14.1.2.6 vulnerable)
  • 13.x (<=13.1.3.4 vulnerable)
  • 12.x (<=12.1.5.2 vulnerable)
  • 11.x (<=11.6.5.2 vulnerable)
  • NOTE: Affects neither BIG-IQ Centralized Management, nor Traffix SDC products.

Detection

Tenable Plugin ID 137918 will detect CVE-2020-5902.  Plugin IDs 137917 and 137915 will detect CVE-2020-5903.

Qualys QIDs 38791 and 373106 will detect CVE-2020-5902.  QID 373107 will detect CVE-2020-5903.

Supporting Information

Subscribe to the deepwatch Insider Blog