dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-32761

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 15.1.10 or later.
See remediation →
74/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
Under certain conditions, a data leak may occur in the Traffic Management Microkernels (TMMs) of BIG-IP tenants running on VELOS and rSeries platforms. This leak occurs randomly and cannot be deliberately triggered. If it occurs, it may leak up to 64 bytes of non-contiguous randomized bytes. Under rare conditions, this may lead to a TMM restart, affecting availability.  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 random data leak vulnerability exists in the Traffic Management Microkernels (TMMs) of BIG-IP tenants running on VELOS and rSeries platforms. Under certain unspecified conditions, up to 64 bytes of non-contiguous randomized memory contents may leak. In rare cases, this can trigger a TMM restart, causing availability impact.

MitigationApply the vendor-supplied software/firmware update for BIG-IP on VELOS and rSeries platforms when available. Monitor for TMM restarts as an indicator of the issue occurring.

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
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10

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
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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
    Check if the BIG-IP system is running on VELOS or rSeries hardware. On the command line, run 'tmsh show sys hardware' or check the system info via the web UI. Look for platform identifiers such as 'VELOS', 'rSeries', or model numbers starting with 'VE' or 'r' in the hardware description.
    Affected if The system is NOT running on VELOS or rSeries hardware - this CVE only applies to those specific platforms.
  2. Check the BIG-IP version
    Run 'tmsh show sys version' or view the version in the web UI under System > Software > Image. Note the version number in the format 15.1.x.
    Affected if The installed version is 15.1.0 through 15.1.9 (inclusive). Versions 15.1.10 and later, or versions below 15.1.0, are not affected.
  3. Verify TMM is running
    Run 'tmsh show sys tmm-info' to confirm the Traffic Management Microkernel is active. Also check 'tmsh show sys tmm' for status.
    Affected if TMM is not running - the vulnerability exists within the TMM process, so an inactive TMM would not be affected by this specific flaw.
  4. Look for recent TMM restarts
    Review TMM restart history by running 'tmsh show sys tmm-stat' and checking the uptime, or examine logs with 'tmsh show sys log daemon' for 'tmm' restart entries. Also check 'tmsh show sys core' for any TMM-related crash files.
    Affected if There have been unexpected TMM restarts or crashes, which in rare cases can be triggered by this memory leak vulnerability.

You are affected only if the BIG-IP system is running on VELOS or rSeries hardware AND the BIG-IP version is 15.1.0 through 15.1.9.

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

Apply the vendor-supplied software/firmware update for BIG-IP on VELOS and rSeries platforms when available. Monitor for TMM restarts as an indicator of the issue occurring.

Recommended fix High confidence

BIG-IP version 15.1.10 or later

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI
  2. 2. Confirm the platform is VELOS or rSeries, as this vulnerability specifically affects these platforms
  3. 3. Review the F5 release notes for version 15.1.10 to understand any compatibility notes or prerequisites
  4. 4. Schedule a maintenance window as the upgrade may require a brief service interruption
  5. 5. Download BIG-IP version 15.1.10 or later from F5 Downloads portal
  6. 6. Follow F5 upgrade procedures: upload the ISO/image, verify integrity, and initiate the upgrade
  7. 7. After upgrade, verify the new version is running: 'tmsh show sys version'
  8. 8. Confirm the TMM processes are stable and monitor for any unexpected restarts

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-32761 — 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-32761 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