The version of F5 Networks BIG-IP installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the K51801290 advisory.

    Systems with microprocessors utilizing speculative execution and that perform speculative reads of system     registers may allow unauthorized disclosure of system parameters to an attacker with local user access via     a side-channel analysis, aka Rogue System Register Read (RSRE), Variant 3a.(CVE-2018-3640)ImpactThere is     no exposure on BIG-IP products by way of the data plane. All exposure is limited to the control plane,     also known as the management plane. Additionally, on the control plane, the vulnerabilities are     exploitable only by the following four authorized, authenticated account roles: Administrator, Resource     Administrator, Manager, and iRules Manager. An attacker must be authorized to access the system in one of     these roles to attempt to exploit the vulnerabilities.This vulnerability requires an attacker who can     provide and run binary code of their choosing on the BIG-IP platform. As a result, these conditions     severely restrict the exposure risk of BIG-IP products.Single-tenancy productsFor single-tenancy products,     such as a standalone BIG-IP device, the risk is limited to a local, authorized user employing one of the     vulnerabilities to read information from memory that they would not normally access, exceeding their     privileges. A user may be able to access kernel-space memory, instead of their own user-space.Multi-     tenancy environmentsFor multi-tenancy environments, such as cloud, Virtual Edition (VE), and Virtual     Clustered Multiprocessing (vCMP), the same local kernel memory access risk applies as in single-tenancy     environments. Additionally, the risk of attacks across guests exists, or attacks against the     hypervisor/host. In cloud and VE environments, preventing these new attacks falls on the hypervisor/host     platform, which is outside the scope of F5's ability to support or patch. Contact your cloud provider or     hypervisor vendor to ensure their platforms or products are protected against Spectre Variants.For vCMP     environments, while the Spectre Variant attacks offer a theoretical possibility of guest-to-guest or     guest-to-host attacks, they are difficult to successfully conduct in the BIG-IP environment. The primary     risk in the vCMP environment with Spectre variants only exists when vCMP guests are configured to use a     single core. If the vCMP guests are configured to use two or more cores, the Spectre Variant     vulnerabilities are eliminated.Vulnerability researchF5 is working with its hardware component vendors to     determine the scope of vulnerabilities across its various generations of hardware platforms. All of the     current information from F5's vendors is represented in this security advisory. F5 is working to obtain     the remaining information from its vendors and will update the security advisory as F5 receives new     information regarding its hardware platforms.F5 is also testing the fixes produced by the Linux community,     and is conducting an extensive test campaign to characterize the impact of the fixes on system performance     and stability to ensure a good experience for its customers. F5 does not want to rush the process and     release fixes without a full understanding of potential issues. Given the limited exposure, the complexity     of the fixes, and the potential issues, a detailed approach is warranted and rushing a fix could result in     an impact to system stability or unacceptable performance costs. F5 will update this article with fixes as     they become available.

Tenable has extracted the preceding description block directly from the F5 Networks BIG-IP security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Detections

Analytics

F5 Networks BIG-IP : RSRE Variant 3a vulnerability (K51801290)

medium Nessus Plugin ID 184245

Version 1.7

Version 1.6

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.0

Version 1.7 Oct 22, 2026, 12:02 AM Detection (corrected module name from AM to AAM; version now includes hotfix level in scan results. corrected version threshold, removing a false positive on a specific hotfix. corrected version ranges across several modules for more accurate detection) Logic Changes (restored a KB flag used by other scan checks. updated to current plugin format. restricts detection to systems with the Configuration utility component installed. restricts detection to affected hardware models. restricts detection to systems with affected components installed) Plugin Feed: 202610220002
Version 1.6 Mar 27, 2025, 11:10 AM CVSS metrics ("Cvssv4 score" set to 0.0) CVSSv2 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202503271110
Version 1.4 Feb 18, 2025, 11:54 PM Plugin metadata (CVSS 3 Change AC:H --> AC:L where needed) Plugin Feed: 202502182354
Version 1.3 Mar 20, 2024, 10:35 PM Plugin metadata (Removed patch_publication_date) Plugin Feed: 202403202235
Version 1.2 Mar 18, 2024, 9:25 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202403182125
Version 1.1 Jan 3, 2024, 4:18 AM Detection (updated detection logic) Plugin Feed: 202401030418
Version 1.0 Nov 2, 2023, 8:18 PM New Plugin Feed: 202311022018