dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-23412

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 16.1.5 / 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 BIG-IP APM Access Profile is configured on a virtual server, undisclosed request 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

This is a denial-of-service vulnerability in F5 BIG-IP APM (Access Policy Manager). When an APM Access Profile is configured on a virtual server, a specific undisclosed request pattern can cause the TMM (Traffic Management Microkernel) process to terminate, disrupting all traffic processing through that virtual server.

MitigationApply F5 security patches when available; meanwhile, restrict access to affected virtual servers using iRule restrictions or network access controls, or consider removing the APM Access Profile from virtual servers where APM functionality is not required.

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 Access Policy ManagerApplication
Affected:>= 16.1.3, < 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. Check BIG-IP version
    Run 'tmsh show sys version' or 'F5 Version' in web UI to determine the installed version.
    Affected if Version is >= 16.1.3 and < 16.1.5, OR >= 17.1.0 and < 17.1.2
  2. Verify APM module is provisioned
    Run 'tmsh show sys provision' and check if 'apm' status is not 'none', or check in the web UI under System > Platform > Provisioning.
    Affected if APM module is provisioned (licensed and enabled)
  3. Identify virtual servers with APM Access Profiles
    Run 'tmsh list ltm virtual one-line' and examine the 'access-profile' or 'access-policy' field, or check in the web UI under Local Traffic > Virtual Servers > Virtual Server List.
    Affected if Any virtual server has an APM Access Profile assigned

If the BIG-IP version falls within the affected ranges AND APM is provisioned AND at least one virtual server has an APM Access Profile configured, the environment is vulnerable to this 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 16.1.5 / 17.1.2 or later
Fixed in 16.1.517.1.2
Interim mitigation

Apply F5 security patches when available; meanwhile, restrict access to affected virtual servers using iRule restrictions or network access controls, or consider removing the APM Access Profile from virtual servers where APM functionality is not required.

Recommended fix High confidence

16.1.5 or 17.1.2 (or later stable releases in respective branches)

  1. 1. Identify all BIG-IP devices running affected versions (16.1.3-16.1.4 or 17.1.0-17.1.1) with APM Access Profiles configured on virtual servers
  2. 2. Download the fixed version (16.1.5 or 17.1.2 or later) from F5 Downloads (downloads.f5.com)
  3. 3. Review F5 release notes for any known issues or prerequisites before upgrading
  4. 4. Plan maintenance window as upgrade may require service interruption
  5. 5. Perform backup of BIG-IP configuration
  6. 6. Upgrade BIG-IP to fixed version 16.1.5 or 17.1.2 or later
  7. 7. Verify APM functionality and TMM processes are running normally after upgrade
Caveat Standard upgrade risks apply - review F5 release notes for any compatibility concerns or behavioral changes

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

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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