dbcve.org
Big Ip Policy Enforcement ManagerApplication · F5

CVE-2025-24497

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 17.1.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 URL categorization is configured on a virtual server, undisclosed requests can cause TMM to terminate.  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

A denial of service vulnerability in F5 products allows remote attackers to cause the Traffic Management Module (TMM) to terminate when URL categorization is configured on a virtual server. The vulnerability is triggered by unspecified requests to the affected virtual server, resulting in service disruption.

MitigationEnable URL categorization only where required and consider deploying rate limiting or traffic filtering as compensating controls until a vendor patch can be 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 Policy Enforcement ManagerApplication
Affected:>= 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. Check BIG-IP version
    Run `tmsh show sys version` or `tmsh show sys hardware` and locate the version string under the software version section
    Affected if Version is 17.1.0, 17.1.1, or any 17.1.x version below 17.1.2
  2. Verify Policy Enforcement Manager module is licensed
    Run `tmsh list sys license` and look for the PEM module in the licensed modules list, or check via the web UI under System > License
    Affected if PEM (Policy Enforcement Manager) appears in the licensed modules
  3. Identify virtual servers with URL categorization configured
    Run `tmsh list ltm virtual` and examine each virtual server for `profile` entries containing `utm` or `url-category` settings, or check via the web UI under Local Traffic > Virtual Servers by viewing the Policy section
    Affected if Any virtual server has a URL categorization or UTM profile assigned
  4. Check for recent TMM crashes
    Run `tmsh show ltm tmm-stats` to view TMM status, and review logs with `tmsh show sys log tmm` for recent crash events or core dumps
    Affected if TMM crashes or core dumps are present in recent logs related to virtual servers with URL categorization
  5. Confirm URL categorization feature is in use
    Review the PEM policy configuration via `tmsh list pem policy` and check for rules that reference URL categories, or examine virtual server profiles for active URL filtering
    Affected if PEM policies contain active URL category rules applied to virtual servers

The environment is affected if the BIG-IP version is 17.1.0 or 17.1.1 and URL categorization is actively configured on any virtual server using the Policy Enforcement Manager module.

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.2 or later
Fixed in 17.1.2
Interim mitigation

Enable URL categorization only where required and consider deploying rate limiting or traffic filtering as compensating controls until a vendor patch can be applied.

Recommended fix High confidence

BIG-IP 17.1.2

  1. 1. Verify current Big IP version by running 'tmsh show sys version' or checking the web UI under System > Software Management > ISO Image
  2. 2. Download BIG-IP 17.1.2 (or later) from the F5 downloads portal at my.f5.com
  3. 3. Review F5 upgrade documentation for your deployment pattern (standalone, HA pair, or cluster)
  4. 4. Create a UCS/BIG-IP config backup before upgrading: 'tmsh save sys ucs /var/local/ucs/pre_upgrade_backup'
  5. 5. Upload the ISO image to the Big IP device via Web UI (System > Software Management > ISO Image) or SCP
  6. 6. Install the new volume using 'tmsh install sys software volume BIGIP-17.1.2' or via the web UI
  7. 7. Reboot the system to activate the new version: 'tmsh reboot'
  8. 8. After reboot, verify the new version is running: 'tmsh show sys version'
Caveat Review F5 release notes for 17.1.2 for any configuration or behavior changes; test in non-production environment first

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

Fix this in Big Ip Policy Enforcement Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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