dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-28889

MEDIUM · 5.9 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 15.1.10.4 / 16.1.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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 an SSL profile with alert timeout is configured with a non-default value on a virtual server, undisclosed traffic along with conditions beyond the attacker's control can cause the Traffic Management Microkernel (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 F5 BIG-IP vulnerability where an SSL profile configured with a non-default alert timeout value on a virtual server can cause the Traffic Management Microkernel (TMM) to terminate unexpectedly, resulting in denial of service. The condition requires specific, undisclosed traffic patterns and factors beyond the attacker's direct control.

MitigationReview SSL profile configurations on virtual servers and either revert alert timeout settings to default values or apply available F5 software patches. Monitor TMM stability after changes.

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.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.4>= 16.1.0, < 16.1.4.3>= 17.1.0, < 17.1.1.3

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 access the web UI under System > Software Management > Volume > Details to see the installed BIG-IP version.
    Affected if The installed version is 15.1.0 to 15.1.10.3, 16.1.0 to 16.1.4.2, or 17.1.0 to 17.1.1.2 (any version before the patched releases).
  2. Identify virtual servers with SSL profiles
    Run 'tmsh list ltm virtual' to list all virtual servers, then filter for those referencing SSL profiles using 'tmsh list ltm virtual <name> ssl profile' or inspect the SSL profile associations in the web UI under Local Traffic > Virtual Servers.
    Affected if Virtual servers are configured that use Client SSL or Server SSL profiles.
  3. Examine SSL profile alert timeout configuration
    Run 'tmsh list ltm profile client-ssl <profile_name>' or 'tmsh list ltm profile server-ssl <profile_name>' to view the profile settings. Look for the 'alert timeout' setting.
    Affected if The alert timeout value is set to a non-default value (default is 'indefinite' or system-defined). A numeric value other than the default indicates a non-default configuration.
  4. Confirm affected virtual server configuration
    Cross-reference virtual servers from step 2 with the SSL profiles from step 3 to identify which virtual servers use SSL profiles with non-default alert timeout values.
    Affected if A virtual server is using an SSL profile where alert timeout is configured to a specific numeric value rather than the default.

You are affected if your BIG-IP version falls within the listed vulnerable ranges AND you have virtual servers configured with SSL profiles that use non-default alert timeout values.

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 15.1.10.4 / 16.1.4.3 / 17.1.1.3 or later
Fixed in 15.1.10.416.1.4.317.1.1.3
Interim mitigation

Review SSL profile configurations on virtual servers and either revert alert timeout settings to default values or apply available F5 software patches. Monitor TMM stability after changes.

Recommended fix High confidence

Upgrade to 15.1.10.4+ for 15.1.x, 16.1.4.3+ for 16.1.x, or 17.1.1.3+ for 17.1.x based on your current major version

  1. 1. Identify the currently installed Big-IP version by running 'tmsh show sys version' or checking the web UI (System > Software).
  2. 2. Navigate to the F5 downloads portal at https://downloads.f5.com/ or access the ISO from your F5 account.
  3. 3. Download the appropriate hotfix for your major version: for 15.1.x download 15.1.10.4 or later, for 16.1.x download 16.1.4.3 or later, for 17.1.x download 17.1.1.3 or later.
  4. 4. Upload the ISO to the Big-IP device via the web UI (System > Software Management > Software Images > Import) or using 'tmsh install sys software' commands.
  5. 5. Create a new boot partition (Volume) for the upgrade using 'tmsh install sys software volume' or the web UI.
  6. 6. Verify the new image is listed and select it as the active boot volume.
  7. 7. Reboot the Big-IP device to load the patched version.
  8. 8. After reboot, confirm the fix by running 'tmsh show sys version' to verify the new version is running.
Caveat Review F5 release notes for any configuration compatibility notes between versions; hotfixes are typically backward compatible but test in staging first

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
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
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,360.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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