dbcve.org
Big Ip Advanced Firewall ManagerApplication · F5

CVE-2025-24312

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 1.4.0 / 15.1.10.6.0.11.6 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 AFM is provisioned with IPS module enabled and protocol inspection profile is configured on a virtual server or firewall rule or policy, undisclosed traffic can cause an increase in CPU 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 AFM (Advanced Firewall Manager) where the IPS module, when enabled with a protocol inspection profile configured on a virtual server or firewall rule/policy, fails to properly handle certain undisclosed traffic patterns. This causes excessive CPU resource consumption, potentially leading to service degradation or complete unavailability.

MitigationDisable protocol inspection profiles on virtual servers or firewall rules/policies when not required, or disable the IPS module if not needed. Monitor CPU utilization and consider upgrading to a patched version when available from F5.

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 Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 16.1.0, < 16.1.5.2.0.7.5>= 17.1.0, < 17.1.2
Big Ip Next Cloud Native Network FunctionsApplication
Affected:>= 1.1.0, < 1.4.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 installed BIG-IP AFM version
    Run 'tmsh show sys version' or access the web UI to view the system version under System > Software Management > ISO Image or System > About. Compare the version number against the affected ranges: 15.1.0 to 15.1.10.6.0.11.6, 16.1.0 to 16.1.5.2.0.7.5, or 17.1.0 to 17.1.2. For Big-IP Next CNF, check version under the instance management interface against 1.1.0 to 1.4.0.
    Affected if The installed version falls within any of the affected version ranges.
  2. Verify AFM module is provisioned
    Run 'tmsh show sys provision' or check via the web UI under System > Resource Provisioning to confirm the Advanced Firewall Manager (AFM) module is provisioned or licensed.
    Affected if AFM is provisioned and licensed on the system.
  3. Confirm IPS module is enabled
    Run 'tmsh list sys ips settings' or access the web UI under Security > Network Intrusion Prevention System (IPS) to verify the IPS module is enabled.
    Affected if IPS is in an enabled or active state.
  4. Identify protocol inspection profiles
    Run 'tmsh list security protocol-inspection profile' or access the web UI under Security > Protocol Security > Inspection Profiles to list all configured protocol inspection profiles.
    Affected if One or more protocol inspection profiles exist in the configuration.
  5. Check if profiles are attached to virtual servers or firewall rules
    Run 'tmsh list ltm virtual' and inspect the 'protocol-inspection-profile' field for each virtual server, or run 'tmsh list security firewall policy' and check for attached protocol inspection profiles.
    Affected if Any virtual server or firewall rule/policy has a protocol inspection profile applied.
  6. Monitor CPU utilization during traffic anomalies
    Observe CPU usage via 'tmsh show sys cpu' or the web UI under Dashboard > Performance. Correlate any unusual CPU spikes with traffic patterns if protocol inspection profiles are in use.
    Affected if Excessive CPU consumption occurs when processing traffic through virtual servers or firewall rules that have protocol inspection enabled.

The environment is affected if the installed version is within the affected ranges, the AFM/IPS module is enabled, and a protocol inspection profile is configured and applied to a virtual server or firewall rule, exposing the system to the DoS condition.

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 1.4.0 / 15.1.10.6.0.11.6 / 16.1.5.2.0.7.5 or later
Fixed in 1.4.015.1.10.6.0.11.616.1.5.2.0.7.5
Interim mitigation

Disable protocol inspection profiles on virtual servers or firewall rules/policies when not required, or disable the IPS module if not needed. Monitor CPU utilization and consider upgrading to a patched version when available from F5.

Recommended fix High confidence

BIG-IP AFM: 15.1.10.6.0.11.6 (15.1.x) | 16.1.5.2.0.7.5 (16.1.x) | 17.1.2 (17.1.x); Big IP Next CNF: 1.4.0

  1. 1. Identify the current BIG-IP AFM version using 'tmsh show sys version' or the web UI
  2. 2. For BIG-IP AFM versions 15.1.x: Upgrade to version 15.1.10.6.0.11.6 or later
  3. 3. For BIG-IP AFM versions 16.1.x: Upgrade to version 16.1.5.2.0.7.5 or later
  4. 4. For BIG-IP AFM versions 17.1.x: Upgrade to version 17.1.2 or later
  5. 5. For Big IP Next Cloud Native Network Functions: Upgrade to version 1.4.0 or later
  6. 6. After upgrade, verify IPS module functionality and monitor CPU utilization under load
  7. 7. Review F5 KB article for any additional post-upgrade configuration requirements
Caveat Review F5 release notes for version-specific notes; ensure IPS module compatibility with your current configuration before upgrading

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

Fix this in Big Ip Advanced Firewall Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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