CVE-2022-41691
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 · uneditedWhen a BIG-IP Advanced WAF/ASM security policy is configured on a virtual server, undisclosed requests can cause the bd process 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 confidenceThis is a denial-of-service vulnerability in F5 BIG-IP where specific undisclosed requests sent to a virtual server configured with a BIG-IP Advanced WAF/ASM security policy can cause the bd (bigd) process to terminate unexpectedly. The attack is network-based and can result 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>= 14.1.0, < 14.1.5.2>= 14.1.0, < 14.1.5.2CVSS 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 'tmsh list /sys version' to determine the installed versionAffected if Version is greater than or equal to 14.1.0 and less than 14.1.5.2
-
Verify ASM or Advanced WAF module is provisionedRun 'tmsh list /sys provision' to see if 'asm' or 'afm' module is provisionedAffected if ASM or Advanced WAF module shows as provisioned (not 'none')
-
Identify virtual servers with security policiesRun 'tmsh list /ltm virtual' and look for entries containing 'security-policy' or 'policy' references under the virtual server configurationAffected if Any virtual server has an ASM or Advanced WAF security policy assigned
-
Check for bigd process crashesReview /var/log/ltm or run 'tmsh show /sys log daemon' for bd or bigd process termination eventsAffected if Logs show unexpected termination of the bd (bigd) process
-
Confirm virtual server is exposed to networkVerify the virtual server is configured with a destination IP and port accessible from the networkAffected if Virtual server with security policy is network-accessible
Environment is affected if BIG-IP version is 14.1.0 through 14.1.5.1, ASM or Advanced WAF is provisioned, and a virtual server has an active security policy exposed to network traffic.
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.5.2
Apply F5 security advisory K24554049 patch or mitigate by disabling/reconfiguring the affected Advanced WAF/ASM security policy on the virtual server until the fix is applied.
14.1.5.2
- Identify the current BIG-IP version using 'tmsh show sys version' or the web UI
- Review the F5 release notes for version 14.1.5.2 for any known issues or prerequisites
- Create a full configuration backup before proceeding with the upgrade
- Upgrade BIG-IP to version 14.1.5.2 or later (15.1.x or 16.x are also options if compatible)
- After upgrade, verify the bd process is running and the security policy functions correctly
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-2022-41691 — 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-41691 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