CVE-2022-41813
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 · uneditedIn versions 16.1.x before 16.1.3.1, 15.1.x before 15.1.6.1, 14.1.x before 14.1.5, and all versions of 13.1.x, when BIG-IP is provisioned with PEM or AFM module, an undisclosed input can cause Traffic Management Microkernel (TMM) to terminate.
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 · moderate confidenceA denial of service vulnerability in F5 BIG-IP allows an attacker to cause the Traffic Management Microkernel (TMM) to terminate when the system is provisioned with the Policy Enforcement Manager (PEM) or Advanced Firewall Module (AFM) modules. The vulnerability is triggered by an undisclosed input and affects multiple version branches including 13.1.x (all versions), 14.1.x before 14.1.5, 15.1.x before 15.1.6.1, and 16.1.x before 16.1.3.1.
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>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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' via TMSH or check the version displayed in the BIG-IP Configuration Utility web UI (System > Software).Affected if Version is 13.1.x (any), 14.1.x before 14.1.5, 15.1.x before 15.1.6.1, or 16.1.x before 16.1.3.1
-
Verify PEM module provisioningRun 'tmsh show sys provision pem' or check System > Resource Provisioning in the web UI for Policy Enforcement Manager status.Affected if PEM module shows as provisioned (any capacity level)
-
Verify AFM module provisioningRun 'tmsh show sys provision afm' or check System > Resource Provisioning in the web UI for Advanced Firewall Manager status.Affected if AFM module shows as provisioned (any capacity level)
-
Confirm affected combinationCross-reference the version check with module provisioning status. Review the affected version ranges and note if either PEM or AFM is provisioned.Affected if Version falls within affected ranges AND either PEM or AFM is provisioned
A system is affected only if it runs a vulnerable BIG-IP version (13.1.x, 14.1.x <14.1.5, 15.1.x <15.1.6.1, or 16.1.x <16.1.3.1) AND has the PEM or AFM module provisioned.
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 · scoped14.1.515.1.6.116.1.3.1
Upgrade BIG-IP to the fixed versions (16.1.3.1, 15.1.6.1, or 14.1.5 or later) to remediate this vulnerability. Systems without PEM or AFM modules provisioned are not affected.
16.1.3.1 or later (16.1.x); 15.1.6.1 or later (15.1.x); 14.1.5 or later (14.1.x); 13.1.x has no fix, requires migration to 14.1.x/15.1.x/16.1.x
- 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI.
- 2. Confirm whether the PEM (Policy Enforcement Manager) or AFM (Advanced Firewall Manager) module is provisioned by running 'tmsh list sys provision' or checking in the web UI under System > Provisioning.
- 3. If either PEM or AFM is provisioned, this vulnerability is applicable.
- 4. Plan for upgrade: backup the current configuration using 'tmsh save sys config' and create a UCS archive using 'tmsh save sys ucs <filename}' for disaster recovery.
- 5. Schedule a maintenance window as upgrades require system downtime.
- 6. Upgrade to the fixed version: 16.1.3.1 or later for 16.1.x, 15.1.6.1 or later for 15.1.x, 14.1.5 or later for 14.1.x. Note: 13.1.x has no fixed version available and requires upgrade to a newer major version.
- 7. After upgrade, verify TMM is running with 'tmsh show sys tmm-status' and confirm the AFM/PEM modules are functional.
- 8. Validate the fix by testing that the previously triggering input no longer causes TMM termination.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41813 — 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-2022-41813 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