basicsecurity.net
Proof, not just disclosure.
Threats / F5 / CVE-2021-22991
CVE-2021-22991 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

F5 BIG-IP Traffic Management Microkernel vulnerability

Buffer overflow in F5 BIG-IP Traffic Management Microkernel allows bypass of URL-based access controls.

Verdict

Today item — known-exploited.

A buffer overflow in the Traffic Management Microkernel component enables attackers to circumvent URL-based access control policies, potentially exposing protected resources. Active exploitation has been observed in the wild.

CISA KEV Yes · 2022-01-183EPSS 0.61064 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-01-18).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.61064 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: F5, BIG-IP Traffic Management Microkernel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious request designed to overflow a buffer in the microkernel's URL processing logic.
Business
Access control policies that should restrict traffic to specific URLs are rendered ineffective.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I send the crafted payload through the BIG-IP appliance to reach protected backend resources.
Business
Unauthorized users gain access to sensitive applications and data that should be restricted by security policies.
3

Lateral reach — past segmentation narrative 3

Attacker
I bypass authentication and authorization checks by exploiting the memory corruption to alter traffic routing decisions.
Business
Compliance violations occur as access logs show policy violations and unauthorized data exposure incidents.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by f5 (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by f5CNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.