SecPod

Learn Search

Search across all Learn content

← Back to Security Research
F5 BIG-IP Devices Under Active Exploitation (CVE-2020-5902)

F5 BIG-IP Devices Under Active Exploitation (CVE-2020-5902)

F5 BIG-IP is a multi-purpose networking device manufactured by F5 Networks which can be configured to work as a traffic shaping system, firewall, load balancer, access gateway, rate limiter, or SSL middleware. F5 BIG-IP devices are one of the most popular networking products and are widely used in g...

Jul 6, 2020By Shakeel Bhat3 min read

F5 BIG-IP is a multi-purpose networking device manufactured by F5 Networks which can be configured to work as a traffic shaping system, firewall, load balancer, access gateway, rate limiter, or SSL middleware. F5 BIG-IP devices are one of the most popular networking products and are widely used in government networks, banks, on the networks of internet service providers, inside cloud computing data centers, and across enterprise networks. Therefore, a Vulnerability Management tool can prevent these attacks.

A critical remote code execution (RCE) CVE-2020-5902 vulnerability has been discovered in F5’s BIG-IP networking devices, which are activelyexploited in the wild. The vulnerability is identified with CVE-2020-5902, allowing an attacker to read files, execute code, or take complete control over a vulnerable system. Moreover, This vulnerability is observing in the wild, being actively in use to install coin miners, IoT malware, or scrape administrator credentials from compromised devices. Vulnerability Management System can resolve these issues.

Vulnerability Details:

The vulnerability resides in the configuration interface, also referred as Traffic Management User Interface – TMUI, of the BIG-IP application delivery controller (ADC). The CVSS score for this vulnerability is 10.0, meaning that the vulnerability is easy to exploit and doesn’t require valid credentials for exploitation. Moreover, An attacker needs to send a specifically crafted HTTP request to the server hosting the Traffic Management User Interface (TMUI) utility for BIG-IP configuration.

A typical HTTP request exploiting f5 big ip vulnerability to fetch contents of ‘/etc/passwd’ file is  below:https:///tmui/login.jsp/..;/tmui/locallb/workspace/fileRead.jsp?fileName=/etc/passwd

On successful exploitation,

exploitation of CVE-2020-5902
exploitation of CVE-2020-5902

F5 has also released fix for an XSS vulnerability in the BIG-IP configuration interface, identified as CVE-2020-5903. This vulnerability allows an authenticated attacker to run a malicious JavaScript code. If the user has administrator privileges and access to Advanced Shell (bash). Successful exploitation can fully compromise BIG-IP via remote code execution.

Publicly available PoC:

Multiple proof-of-concept codes are publicly available for the vulnerability.

Impact:

This vulnerability allows an attacker to create or delete files, disable services, intercept information, run arbitrary system commands and Java code. Completely compromise the system, directory traversal exploitation and pursue further targets, such as the internal network.

Affected Versions:

BIG-IP Devices (LTM, AAM, AFM, Analytics, APM, ASM, DNS, FPS, GTM, Link Controller, PEM) versions. 11.6.x prior to 11.6.5.2, 12.1.x prior to 12.1.5.2, 13.x prior to 13.1.3.4, 14.x prior to 14.1.2.6 and 15.x prior to 15.1.0.4.

Solution for CVE-2020-5902:

F5 has released security fixes for these vulnerabilities. Updrage BIG-IP Devices (LTM, AAM, AFM, Analytics, APM, ASM, DNS, FPS, GTM, Link Controller, PEM) to version:

  • 11.6.5.2, or
  • 12.1.5.2, or
  • 13.1.3.4, or
  • 14.1.2.6, or
  • 15.1.0.4

Mitigation:NOTE: This is a temporary workaround. Please apply the above solution as early as possible.

Following mitigations are available:

  • All network interfaces: This can be of use to address the primary threat from unauthenticated attackers.
  • Self IPs: This addresses unauthenticated and authenticated attackers on self-IPs by blocking all access.
  • Management interface: This addresses unauthenticated attackers on management interface by restricting access.

Therefore, Please refer to Mitigation Section in vendor-advisory for step-by-step details.

Featured Posts

Open CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials
CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

CVE Research

CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

Two MikroTik RouterOS CVEs entered CISA KEV seven days after production fixes. Dated reporting places SSH-chain exploitation involving CVE-2026-86060 at least one calendar day before those releases; no comparable start date is established for CVE-2026-67277.

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch
Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

CVE Research

Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

Four vulnerabilities added to CISA’s KEV catalog on September 9, 2026 show widely different timelines between public disclosure and formal exploitation-based prioritization, ranging from one day to 239 days.

Sep 24, 2026

Open TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

CVE Research

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

A chronological look at how a long-running China-nexus espionage cluster evolved from server-side exploitation to a chained Chrome/Windows zero-day kit — and what that shift signals.

Sep 24, 2026