Big Ip Access Policy ManagerApplication · F5
CVE-2024-24775
A fix is available.
Upgrade to 15.1.9 / 16.1.4 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 · uneditedWhen a virtual server is enabled with VLAN group and SNAT listener is configured, undisclosed traffic 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 · low confidenceDeveloping — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.
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.9>= 16.1.0, < 16.1.4= 17.1.0
Big Iq Centralized ManagementApplication
Affected:
>= 8.0.0, <= 8.3.0
Big Ip Advanced Firewall ManagerApplication
Affected:
>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip AnalyticsApplication
Affected:
>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Application Acceleration ManagerApplication
Affected:
>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Application Security ManagerApplication
Affected:
>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Domain Name SystemApplication
Affected:
>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Fraud Protection ServiceApplication
Affected:
>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0CVSS 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
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.9 / 16.1.4 or later
Fixed in
15.1.916.1.4
Recommended fix
High confidence
Big IP 15.1.x -> 15.1.9+; Big IP 16.1.x -> 16.1.4+; Big IP 17.1.0 -> 17.1.1+; Big Iq CM 8.x -> check F5 for patched release
- 1. Identify the exact Big IP product module(s) and version(s) running in your environment using 'tmsh show sys version'
- 2. For Big IP versions 15.1.x: Plan upgrade to version 15.1.9 or later
- 3. For Big IP versions 16.1.x: Plan upgrade to version 16.1.4 or later
- 4. For Big IP version 17.1.0: Plan upgrade to version 17.1.1 or later
- 5. For Big Iq Centralized Management 8.0.0-8.3.0: Check F5 support for available patches or upgrade path
- 6. Schedule maintenance window and backup configuration using 'tmsh save sys config'
- 7. Perform upgrade following F5 upgrade documentation for your specific product
- 8. After upgrade, verify virtual server configuration with VLAN groups and SNAT listeners still functions correctly
Caveat Review F5 release notes for between-version differences; some legacy configurations may behave differently in newer major versions
Generated from the published advisory — verify against the referenced sources before acting.
We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200.
Get the upgrade done
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2024-24775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24775 in production — separate from our analysis above.
Know something about CVE-2024-24775?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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