dbcve.org
Big Ip Advanced Web Application FirewallApplication · F5

CVE-2022-41836

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 15.1.7 / 16.1.3.1 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 an 'Attack Signature False Positive Mode' enabled 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 the 'bd' (BIG-IP daemon) process terminates when specific undisclosed requests are processed by a virtual server with 'Attack Signature False Positive Mode' enabled in its security policy. The vulnerability has a CVSS base score of 7.5, indicating high severity.

MitigationDisable 'Attack Signature False Positive Mode' on affected security policies until a vendor patch is available, or apply the latest F5 BIG-IP security updates.

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:>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1= 17.0.0
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.1= 17.0.0

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 F5 BIG-IP version
    Run 'tmsh show sys version' or view the System > Software Management > ISO Image page in the web UI to determine the installed version.
    Affected if The version is 15.1.0 to 15.1.6, 16.1.0 to 16.1.3.0, or exactly 17.0.0.
  2. Verify Application Security Manager is provisioned
    Run 'tmsh list sys provision asm' or check System > Resource Provisioning in the web UI to see if ASM is provisioned.
    Affected if ASM is provisioned and running.
  3. Identify virtual servers with security policies
    Run 'tmsh list ltm virtual' and for each virtual server, check if it references a security policy with 'tmsh list asm policy <policy_name>' or via the web UI at Security > Application Security > Policies.
    Affected if Virtual servers exist with attached ASM security policies.
  4. Check if Attack Signature False Positive Mode is enabled
    For each ASM policy, run 'tmsh list asm policy <policy_name>' and look for 'attack-signature-false-positive-mode enabled' or inspect the policy in the web UI under Security > Application Security > Policy > Attack Signature Settings.
    Affected if Any security policy has 'Attack Signature False Positive Mode' set to enabled.

A user is affected if their BIG-IP runs a vulnerable version (15.1.0-15.1.6, 16.1.0-16.1.3.0, or 17.0.0), has ASM provisioned, and has at least one security policy with Attack Signature False Positive Mode enabled on a virtual server.

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 15.1.7 / 16.1.3.1 or later
Fixed in 15.1.716.1.3.1
Interim mitigation

Disable 'Attack Signature False Positive Mode' on affected security policies until a vendor patch is available, or apply the latest F5 BIG-IP security updates.

Recommended fix High confidence

15.1.7 for 15.1.x releases; 16.1.3.1 for 16.1.x releases; 17.1.0 or later for 17.0.0

  1. Identify the current BIG-IP version using 'tmsh show sys version' or the web management console
  2. Determine which affected product (Advanced Web Application Firewall or Application Security Manager) is deployed
  3. Schedule a maintenance window for the upgrade
  4. Download the appropriate fixed version from F5 Downloads (15.1.7, 16.1.3.1, or a later 17.x release)
  5. Backup the current configuration using 'tmsh save sys config'
  6. Upload and install the new version via the web management console or via tmsh
  7. Verify the bd process is running after reboot using 'tmsh show sys process bd'
  8. Confirm the security policy with 'Attack Signature False Positive Mode' is functioning correctly
Caveat Review F5 release notes for the target version to check for compatibility with other deployed modules and any behavior changes

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
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41836 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-41836 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