CVE-2021-23044
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 version 16.x before 16.1.0, 15.1.x before 15.1.3.1, 14.1.x before 14.1.4.2, 13.1.x before 13.1.4.1, and all versions of 12.1.x and 11.6.x, when the Intel QuickAssist Technology (QAT) compression driver is used on affected BIG-IP hardware and BIG-IP Virtual Edition (VE) platforms, undisclosed traffic can cause the Traffic Management Microkernel (TMM) 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 exists in F5 BIG-IP devices when Intel QuickAssist Technology (QAT) compression driver is enabled. Undisclosed traffic patterns can cause the Traffic Management Microkernel (TMM) to terminate, resulting in service disruption.
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>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3.1>= 16.0.0, < 16.1.0CVSS 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.
-
Check BIG-IP versionRun 'tmsh show /sys version' or view /etc/product_version to obtain the installed versionAffected if The version falls within 11.6.0-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4.1, 14.1.0-14.1.4.2, 15.1.0-15.1.3.1, or 16.0.0-16.1.0
-
Identify enabled BIG-IP modulesRun 'tmsh show /cm device' to list installed modules such as APM, AFM, Analytics, AAM, ASM, DNS, GTMAffected if Any of these modules are provisioned and the version is in the affected range
-
Verify QAT compression driver statusCheck the Traffic Management Microkernel (TMM) configuration via 'tmsh show /ltm profile compression' or inspect whether the Intel QuickAssist Technology (QAT) compression driver is enabled in the systemAffected if QAT compression driver is enabled in the configuration
The environment is affected if the BIG-IP version is within the affected ranges AND QAT compression driver is enabled, as the vulnerability only triggers when QAT is active.
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 · scoped13.1.4.114.1.4.215.1.3.1
Upgrade BIG-IP to version 16.1.0 or later (15.1.3.1+, 14.1.4.2+, 13.1.4.1+) or disable QAT compression if upgrade is not feasible.
Upgrade to 14.1.4.2 or later (14.1.x); 13.1.4.1 or later (13.1.x); 15.1.3.1 or later (15.1.x); 16.1.0 or later (16.x). For 11.6.x and 12.1.x versions, these have reached End of Technical Support (EoTS) and require upgrading to a supported version.
- Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web management console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23044 — 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-23044 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