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

F5 BIG-IP vulnerability

F5 BIG-IP missing authentication vulnerability allows unauthenticated remote code execution, file manipulation, and service disruption.

Verdict

Today item, not a backlog item.

Critical missing authentication flaw in F5 BIG-IP enables remote attackers to execute arbitrary code, modify or delete files, and disable services without credentials. Active exploitation and ransomware deployment observed.

CISA KEV Yes · 2022-05-103Ransomware use Flagged3EPSS 0.99956 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
851 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-05-10), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99956 — 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. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-306 · Missing AuthenticationAuthentication
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 identify the F5 BIG-IP instance and send a crafted request to a critical function lacking authentication checks.
Business
Attacker gains initial network access to a critical infrastructure component with no authentication barrier.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary code on the compromised BIG-IP system to establish persistence and lateral movement.
Business
Attacker achieves code execution within the load balancer, potentially pivoting to protected backend systems.
3

Lateral reach — past segmentation narrative 3

Attacker
I manipulate or delete configuration files and disable BIG-IP services to disrupt traffic flow.
Business
Organization experiences service outages affecting all traffic routed through the compromised load balancer.
4

Data at risk — exfiltration narrative 4

Attacker
I deploy ransomware payloads across the infrastructure using the compromised BIG-IP as an entry point.
Business
Ransomware spreads to critical systems; organization faces encryption of data and operational shutdown.
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)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 851 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • 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.