dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-41164

HIGH · 7.5 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 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 TCP profile with Multipath TCP enabled (MPTCP) is configured on a Virtual Server, undisclosed traffic along with conditions beyond the attackers control 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 where enabling Multipath TCP (MPTCP) on a TCP profile attached to a Virtual Server can cause the TMM (Traffic Management Module) to crash when certain undisclosed traffic patterns are encountered. The condition is not reliably exploitable due to factors beyond attacker control.

MitigationIf MPTCP is not required, disable it on affected TCP profiles. Otherwise, ensure traffic filtering and rate limiting are in place to reduce likelihood of triggering the condition, and monitor for TMM crashes.

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:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip AnalyticsApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.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 F5 BIG-IP version
    Run 'tmsh show sys version' or view the version in the web UI under Dashboard > Overview
    Affected if The installed version falls within 15.1.0-15.1.1, 16.1.0-16.1.4, or equals 17.1.0
  2. Identify TCP profiles with MPTCP enabled
    Run 'tmsh list ltm profile tcp' and look for entries containing 'multipath enabled' or 'multipath dynamic' under the profile settings
    Affected if Any TCP profile shows multipath enabled or multipath dynamic mode
  3. Check if MPTCP-enabled profiles are assigned to Virtual Servers
    Run 'tmsh list ltm virtual' and cross-reference with the profiles found in step 2. For each virtual server, examine the 'profiles' section to see if it references an MPTCP-enabled TCP profile
    Affected if Any Virtual Server is using a TCP profile that has MPTCP enabled

You are affected if your BIG-IP version is within the vulnerable range AND you have a TCP profile with MPTCP enabled attached to a Virtual Server, as the crash requires MPTCP to be configured and active on traffic flowing through a virtual server.

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

If MPTCP is not required, disable it on affected TCP profiles. Otherwise, ensure traffic filtering and rate limiting are in place to reduce likelihood of triggering the condition, and monitor for TMM crashes.

Recommended fix High confidence

16.1.5 or later (16.1.x line); 17.1.1 or later (17.1.x line); latest hotfix for 15.1.x (contact F5)

  1. 1. Identify all Virtual Servers using a TCP profile with MPTCP (Multipath TCP) enabled
  2. 2. Check the current BIG-IP version by running 'tmsh show sys version' or viewing the web UI dashboard
  3. 3. For BIG-IP 16.1.x systems: Upgrade to version 16.1.5 or later
  4. 4. For BIG-IP 15.1.x systems: Upgrade to the latest hotfix that includes the fix for this vulnerability (contact F5 support for specific hotfix)
  5. 5. For BIG-IP 17.1.0 systems: Upgrade to 17.1.1 or later
  6. 6. After upgrade, verify MPTCP functionality is working correctly and TMM is stable
Caveat Review F5 release notes for 16.1.5 and 17.1.1 for any compatibility changes before upgrading

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
  • 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-2024-41164 — 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-41164 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