Big Ip Advanced Web Application FirewallApplication · F5

CVE-2022-41691

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 14.1.5.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
When 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 confidence

This 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.

MitigationApply 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.

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
Big Ip Advanced Web Application FirewallApplication
Affected:>= 14.1.0, < 14.1.5.2
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0, < 14.1.5.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP version
    Run 'tmsh show /sys version' or 'tmsh list /sys version' to determine the installed version
    Affected if Version is greater than or equal to 14.1.0 and less than 14.1.5.2
  2. Verify ASM or Advanced WAF module is provisioned
    Run 'tmsh list /sys provision' to see if 'asm' or 'afm' module is provisioned
    Affected if ASM or Advanced WAF module shows as provisioned (not 'none')
  3. Identify virtual servers with security policies
    Run 'tmsh list /ltm virtual' and look for entries containing 'security-policy' or 'policy' references under the virtual server configuration
    Affected if Any virtual server has an ASM or Advanced WAF security policy assigned
  4. Check for bigd process crashes
    Review /var/log/ltm or run 'tmsh show /sys log daemon' for bd or bigd process termination events
    Affected if Logs show unexpected termination of the bd (bigd) process
  5. Confirm virtual server is exposed to network
    Verify the virtual server is configured with a destination IP and port accessible from the network
    Affected 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.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 14.1.5.2 or later
Fixed in 14.1.5.2
Interim mitigation

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.

Recommended fix High confidence

14.1.5.2

  1. Identify the current BIG-IP version using 'tmsh show sys version' or the web UI
  2. Review the F5 release notes for version 14.1.5.2 for any known issues or prerequisites
  3. Create a full configuration backup before proceeding with the upgrade
  4. Upgrade BIG-IP to version 14.1.5.2 or later (15.1.x or 16.x are also options if compatible)
  5. 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.

Fix this in Big Ip Advanced Web Application Firewall Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41691 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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