CVE-2021-23030
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOn BIG-IP Advanced WAF and BIG-IP ASM version 16.0.x before 16.0.1.2, 15.1.x before 15.1.3.1, 14.1.x before 14.1.4.3, 13.1.x before 13.1.4.1, and all versions of 12.1.x, when a WebSocket profile is configured on a virtual server, undisclosed requests can cause bd to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial of service vulnerability in F5 BIG-IP Advanced WAF and ASM allows remote attackers to crash the bigd daemon by sending specially crafted WebSocket requests to virtual servers that have a WebSocket profile configured. The vulnerability affects multiple version branches including 12.1.x (all versions), 13.1.x before 13.1.4.1, 14.1.x before 14.1.4.3, 15.1.x before 15.1.3.1, and 16.0.x before 16.0.1.2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.0.1.1>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.0.0, <= 16.0.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed BIG-IP versionRun command: tmsh show sys version or check the BIG-IP web UI under System > Software Management > ISO Image (shows installed version)Affected if The version falls within 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4, 15.1.0-15.1.3, or 16.0.0-16.0.1.1
-
Confirm the BIG-IP module is Advanced WAF or ASMRun command: tmsh list sys module or check the license information in the web UI under System > LicenseAffected if The BIG-IP module license includes Application Security Manager (ASM) or Advanced WAF
-
Check for configured WebSocket profilesRun command: tmsh list ltm profile websocket or inspect virtual servers via web UI under Local Traffic > Virtual Servers > ProfilesAffected if Any WebSocket profile exists and is assigned to a virtual server
-
Identify virtual servers using WebSocket profilesRun command: tmsh list ltm virtual all one-line | grep -i websocket or review virtual server configuration in the web UIAffected if A virtual server references a WebSocket profile
The system is vulnerable if it runs a affected BIG-IP version (12.1.x, 13.1.x before 13.1.4.1, 14.1.x before 14.1.4.3, 15.1.x before 15.1.3.1, or 16.0.x before 16.0.1.2) with ASM/Advanced WAF module and has a WebSocket profile assigned to any virtual server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade BIG-IP to the fixed versions (16.0.1.2+, 15.1.3.1+, 14.1.4.3+, 13.1.4.1+) or disable WebSocket profiles on affected virtual servers if upgrade is not immediately feasible.
Upgrade to 16.0.1.2 (for 16.0.x), 15.1.3.1 (for 15.1.x), 14.1.4.3 (for 14.1.x), or 13.1.4.1 (for 13.1.x). Note: 12.1.x has no fix and is EoTS.
- Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI
- Determine which BIG-IP product (Advanced WAF or ASM) is affected and which version branch (12.1.x, 13.1.x, 14.1.x, 15.1.x, or 16.0.x) is in use
- For 12.1.x versions: No fix available; this version is End of Technical Support (EoTS) and requires upgrade to a supported version
- For 16.0.x: Upgrade to version 16.0.1.2 or later
- For 15.1.x: Upgrade to version 15.1.3.1 or later
- For 14.1.x: Upgrade to version 14.1.4.3 or later
- For 13.1.x: Upgrade to version 13.1.4.1 or later
- Download the appropriate hotfix from support.f5.com after logging in with valid credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-23030 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data