dbcve.org
Big Ip Advanced Web Application FirewallApplication · F5

CVE-2024-23308

HIGH · 7.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 17.1.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 a BIG-IP Advanced WAF or BIG-IP ASM policy with a Request Body Handling option is attached to a virtual server, undisclosed requests can cause the BD process to terminate. The condition results from setting the Request Body Handling option in the Header-Based Content Profile for an Allowed URL with "Apply value and content signatures and detect threat campaigns."  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 confidence

A denial of service vulnerability exists in F5 BIG-IP Advanced WAF and ASM where specifically configured Request Body Handling in a Header-Based Content Profile for an Allowed URL causes the BD (BigDB/BufferDB) process to terminate. The condition is triggered when the option 'Apply value and content signatures and detect threat campaigns' is selected.

MitigationModify the WAF/ASM policy to remove or reconfigure the Request Body Handling setting in the Header-Based Content Profile for affected Allowed URLs, or apply vendor-supplied patches if available.

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:>= 17.1.0, < 17.1.1
Big Ip Application Security ManagerApplication
Affected:>= 17.1.0, < 17.1.1

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' command or check via Configuration utility under System > Software Management > ISO Image
    Affected if Version is 17.1.0 (versions >= 17.1.0 and < 17.1.1 are affected)
  2. Verify WAF/ASM module is provisioned
    Run 'tmsh show sys provision' or check in Configuration utility under System > Resource Provisioning
    Affected if WAF or ASM module is provisioned (the vulnerability exists in the ASM component)
  3. Identify WAF policies with Header-Based Content Profiles
    Review WAF security policies in Configuration utility under Security > Application Security > Security Policies, or list policies via 'tmsh list asm policy' and examine Allowed URLs for Header-Based Content Profile assignments
    Affected if Any security policy contains Allowed URLs configured with Header-Based Content Profiles
  4. Inspect Request Body Handling configuration
    For each Header-Based Content Profile found on Allowed URLs, navigate to Request Body Handling settings and check if the option 'Apply value and content signatures and detect threat campaigns' is enabled
    Affected if This specific option is selected in the Request Body Handling settings for a Header-Based Content Profile

A system is affected if it runs BIG-IP version 17.1.0, has WAF/ASM provisioned, and contains a security policy with a Header-Based Content Profile on an Allowed URL where Request Body Handling has 'Apply value and content signatures and detect threat campaigns' enabled.

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 17.1.1 or later
Fixed in 17.1.1
Interim mitigation

Modify the WAF/ASM policy to remove or reconfigure the Request Body Handling setting in the Header-Based Content Profile for affected Allowed URLs, or apply vendor-supplied patches if available.

Recommended fix High confidence

BIG-IP 17.1.1 or later

  1. 1. Backup the current BIG-IP configuration using 'tmsh save sys config' command.
  2. 2. Verify the current BIG-IP version using 'tmsh show sys version' command.
  3. 3. Download BIG-IP version 17.1.1 or later from the F5 Downloads portal (my.f5.com).
  4. 4. Upload the ISO image to the BIG-IP device using SCP or the web management interface.
  5. 5. Install the new volume using 'tmsh install sys volume' command with the downloaded image.
  6. 6. Boot into the new volume and verify the upgrade was successful using 'tmsh show sys version'.
  7. 7. Test the Advanced WAF/ASM policies to confirm functionality is restored.
  8. 8. Confirm the BD process is stable and not terminating under load.
Caveat Review F5 release notes for 17.1.1 for any configuration or behavioral changes before upgrading, as some settings may need adjustment

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23308 — 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-2024-23308 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