dbcve.org
Big Ip Application Security ManagerApplication · F5

CVE-2025-24326

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 15.1.10.6.0.11.6-ENG / 16.1.5 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 BIG-IP Advanced WAF/ASM Behavioral DoS (BADoS) TLS Signatures feature is configured, undisclosed traffic can case an increase in memory resource utilization. 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 · moderate confidence

This is a denial-of-service vulnerability in F5 BIG-IP Advanced WAF/ASM's Behavioral DoS (BADoS) TLS Signatures feature. When this feature is configured, specific undisclosed traffic patterns trigger excessive memory allocation, potentially leading to memory exhaustion and service degradation or failure.

MitigationApply the vendor patch when available. In the interim, consider disabling or restricting the BADoS TLS Signatures feature if operationally feasible, and monitor memory utilization closely.

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 Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6-ENG>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.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. Verify BIG-IP ASM version
    Check the installed version of F5 BIG-IP Application Security Manager (ASM) using the web UI (System > Software Management > Image List) or tmsh command 'show sys version'. Compare this version against the affected ranges: 15.1.0 to 15.1.10.6.0.11.6-ENG, 16.1.0 to 16.1.5, and 17.1.0 to 17.1.2.
    Affected if The installed version falls within any of the listed vulnerable version ranges.
  2. Confirm ASM module provisioning
    Verify that the Application Security Manager module is provisioned on the BIG-IP system. Use the web UI (System > Resource Provisioning) or run 'tmsh show sys provision' to check the provisioning status of ASM.
    Affected if ASM is provisioned and running.
  3. Check BADoS TLS Signatures configuration
    Navigate to the Behavioral DoS (BADoS) configuration in the BIG-IP ASM web UI (Security > DoS Protection > Device Configuration > Behavioral DoS). Inspect whether the TLS Signatures feature is enabled within the BADoS profile.
    Affected if The TLS Signatures feature in BADoS is enabled and configured.
  4. Monitor memory utilization
    Observe system memory usage over time using the web UI (Statistics > Performance > Throughput) or via tmsh command 'show sys memory'. Look for abnormal or steadily increasing memory consumption that correlates with the BADoS feature processing traffic.
    Affected if Memory usage is unusually high or continuously growing while the BADoS TLS Signatures feature is active.

You are affected if you are running a vulnerable ASM version (15.1.x, 16.1.x, or 17.1.x within the specified ranges) with the BADoS TLS Signatures feature enabled and are experiencing elevated memory usage.

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.10.6.0.11.6-ENG / 16.1.5 / 17.1.2 or later
Fixed in 15.1.10.6.0.11.6-ENG16.1.517.1.2
Interim mitigation

Apply the vendor patch when available. In the interim, consider disabling or restricting the BADoS TLS Signatures feature if operationally feasible, and monitor memory utilization closely.

Recommended fix High confidence

15.1.10.6.0.11.6-ENG (or later 15.1.x) / 16.1.5 (or later 16.1.x) / 17.1.2 (or later 17.1.x)

  1. 1. Identify the currently deployed BIG-IP ASM version using 'tmsh show sys version' or the web management console.
  2. 2. Based on the current version branch, plan upgrade to the fixed release: For 15.1.x branch, upgrade to 15.1.10.6.0.11.6-ENG or later; For 16.1.x branch, upgrade to 16.1.5 or later; For 17.1.x branch, upgrade to 17.1.2 or later.
  3. 3. Before upgrading, review F5 release notes for the target version to confirm the CVE fix is included.
  4. 4. Perform a backup of the BIG-IP configuration using 'tmsh save sys config' or the web UI.
  5. 5. Download the target version ISO from F5 Networks (my.f5.com) and upload to the BIG-IP.
  6. 6. Follow F5 upgrade procedures: boot from ISO or use Volume Manager, then install the new version.
  7. 7. After upgrade, verify the BIG-IP ASM Behavioral DoS TLS Signatures feature functions correctly.
  8. 8. Confirm the vulnerability is remediated by checking that memory utilization remains stable under the same traffic conditions.
Caveat Minor: Review F5 release notes for any behavioral changes; backup configuration before upgrading; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Application Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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