IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2021-22991|Auth: none — unauthenticated|Reboot: required|Manual only

F5 BIG-IP Traffic Management Microkernel Buffer Overflow (CVE-2021-22991)

The Traffic Management Microkernel of BIG-IP ASM Risk Engine has a buffer overflow vulnerability, leading to a bypassing of URL-based access controls.

Published Mar 31, 2021 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2022-02-01 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Buffer Overflow (CWE-119) vulnerability in F5 BIG-IP Traffic Management Microkernel. On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.1.x before 12.1.5.3, undisclosed requests to a virtual server may be incorrectly handled by the Traffic Management Microkernel (TMM) URI normalization, which may trigger a buffer overflow, resulting in a DoS attack. In certain situations, it may theoretically allow bypass of URL based access control or remote code execution (RCE). Note: Software versions which have reached End of Software Development (EoSD) are not evaluated. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

IT Security
Running big-ip access policy manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip advanced firewall manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip advanced web application firewall: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip analytics: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip application acceleration manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip application security manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip ddos hybrid defender: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip domain name system: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip fraud protection service: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip global traffic manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip link controller: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip local traffic manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; big-ip policy enforcement manager: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1; ssl orchestrator: 12.1.0 ≤ v < 12.1.5.3, 13.1.0 ≤ v < 13.1.3.6, 14.1.0 ≤ v < 14.1.4, 15.1.0 ≤ v < 15.1.2.1, 16.0.0 ≤ v < 16.0.1.1
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2022-01-18 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2022-02-01.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2021-22991's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.