dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-41727

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
In BIG-IP tenants running on r2000 and r4000 series hardware, or BIG-IP Virtual Edition (VEs) using Intel E810 SR-IOV NIC, undisclosed traffic can cause 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

A memory resource exhaustion vulnerability exists in BIG-IP tenants running on r2000 and r4000 series hardware, as well as BIG-IP Virtual Edition instances using Intel E810 SR-IOV NICs. When specific undisclosed traffic patterns are processed, memory utilization increases abnormally, potentially leading to denial of service conditions.

MitigationApply the vendor-provided patch or update to BIG-IP software that addresses this memory exhaustion issue. For systems that cannot be immediately patched, consider implementing traffic filtering or rate limiting as a temporary workaround until the fix can be deployed.

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. Identify the hardware platform or virtualization environment
    Run 'tmsh show sys hardware' and look for r2000 or r4000 series platform information. For Virtual Edition, check the hypervisor and NIC configuration for Intel E810 SR-IOV usage.
    Affected if The system is running on r2000 or r4000 series hardware, or is a Virtual Edition instance using Intel E810 SR-IOV NICs.
  2. Determine the installed BIG-IP software version
    Run 'tmsh show sys version' or check the BIG-IP login page/version banner. Compare the version against the affected ranges: 15.1.0-15.1.1, 16.1.0-16.1.4, or 17.1.0.
    Affected if The installed version falls within any of the affected version ranges.
  3. Confirm the specific BIG-IP module in use
    Run 'tmsh list sys provision' to see which modules are provisioned (APM, AFM, ASM, Analytics, AAM, AVR, or Automation Toolchain).
    Affected if Any of the listed affected modules (APM, AFM, AWM, Analytics, AAM, ASM, AVR, Automation Toolchain) are provisioned on the affected version.
  4. Check for abnormal memory utilization patterns
    Monitor memory usage via 'tmsh show sys memory' or 'tmsh show ltm node all detail' over time. Look for unexpected growth in memory consumption that correlates with specific traffic patterns.
    Affected if Memory utilization increases abnormally during processing of specific traffic patterns, especially under sustained load.
  5. Review system logs for denial of service indicators
    Check /var/log/ltm and /var/log/system for memory exhaustion errors, tmm crashes, or service disruptions that coincide with traffic spikes.
    Affected if Logs show memory-related failures or tmm restarts without an obvious cause, indicating potential memory exhaustion.

A system is affected if it runs on r2000/r4000 hardware or Virtual Edition with Intel E810 SR-IOV, is running any affected BIG-IP version (15.1.0-15.1.1, 16.1.0-16.1.4, or 17.1.0), and has an affected module provisioned.

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

Apply the vendor-provided patch or update to BIG-IP software that addresses this memory exhaustion issue. For systems that cannot be immediately patched, consider implementing traffic filtering or rate limiting as a temporary workaround until the fix can be deployed.

Recommended fix High confidence

Upgrade to the next available maintenance release: 15.1.2+ (15.1.x LTS), 16.1.5+ (16.1.x LTS), or 17.1.1+ (17.1.x)

  1. 1. Identify the current BIG-IP version by running `tmsh show sys version` or checking the web UI at System > Software > BIG-IP Version
  2. 2. For BIG-IP 15.1.x deployments: Upgrade to version 15.1.2 or later (15.1.5.5 or latest 15.1.x LTS is recommended)
  3. 3. For BIG-IP 16.1.x deployments: Upgrade to version 16.1.5 or later (16.1.5.5 or latest 16.1.x LTS is recommended)
  4. 4. For BIG-IP 17.1.x deployments: Upgrade to version 17.1.1 or later (17.1.1.2 or latest 17.1.x is recommended)
  5. 5. Download the appropriate hotfix from the F5 Downloads page (my.f5.com) or via the F5 cloud services portal
  6. 6. Follow F5 standard upgrade procedures: backup current configuration via `tmsh save sys config`, verify checksum of downloaded ISO, and perform upgrade via GUI or `tmsh install sys software`
  7. 7. After upgrade, verify the fix by checking memory utilization remains stable under normal traffic patterns
  8. 8. Monitor for any regression issues post-upgrade
Caveat Standard F5 upgrade precautions apply - review release notes for any known issues, test in staging environment first, and ensure valid configuration backup before proceeding

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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