Loading vulnerability…
CVE-2021-22991 is a buffer overflow vulnerability in F5 BIG-IP affecting the Traffic Management Microkernel (TMM) URI normalization logic. On vulnerable BIG-IP releases, undisclosed requests sent to a virtual server can be incorrectly handled during URI normalization, causing memory corruption in TMM and triggering a buffer overflow. The primary documented outcome is denial of service. F5 also indicated that, in certain situations, the flaw may theoretically permit bypass of URL-based access controls or remote code execution. The issue affects BIG-IP 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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A buffer overflow vulnerability in F5 BIG-IP that the MANGA Mirai variant attempts to exploit.
Kriittinen puskuriylivuoto TMM-komponentissa, joka voi johtaa palvelunestoon (DoS).
A buffer overflow caused by incorrect URI normalization in an application traffic product; notable because the content explicitly says it was exploited in the wild.
Critical buffer overflow vulnerability in F5 BIG-IP’s Traffic Management Microkernel (TMM) triggered by undisclosed request handling, potentially leading to crash/DoS and possibly code execution depending on exploitability (not specified here).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.