dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-22093

HIGH · 8.7 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 15.1.9 / 16.1.4 or later.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable 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 running in appliance mode, an authenticated remote command injection vulnerability exists in an undisclosed iControl REST endpoint on multi-bladed systems. A successful exploit can allow the attacker to cross a security boundary.  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

An authenticated remote command injection vulnerability exists in the iControl REST API on F5 multi-bladed systems running in appliance mode. The vulnerability resides in an undisclosed REST endpoint and allows authenticated attackers to execute arbitrary commands, potentially enabling privilege escalation and lateral movement across security boundaries.

MitigationApply the vendor-provided patch for affected versions; multi-bladed systems in appliance mode should be prioritized given the boundary-crossing capability. Identify and upgrade any EoTS versions to supported releases.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

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 F5 product and version
    Run 'tmsh show sys version' or check the Big-IP or Big-IQ system version through the management interface or API
    Affected if The installed version falls within 15.1.0 to 15.1.8, 16.1.0 to 16.1.3, or equals 17.1.0 for the affected module
  2. Determine if the system is multi-bladed
    Check the system hardware configuration using 'tmsh show sys hardware' or review the chassis information to confirm multiple blades are present
    Affected if The system has multiple blades installed and is not a single-blade or virtual edition
  3. Verify appliance mode is enabled
    Run 'tmsh show sys license' or check the system licensing information to confirm appliance mode is active
    Affected if Applice mode is enabled on a multi-bladed system (this is the required condition for the vulnerability to be exploitable)
  4. Confirm iControl REST API exposure
    Check if the iControl REST API service is running and accessible by reviewing the BIG-IP REST API service status or checking port 443 accessibility
    Affected if The iControl REST API is exposed and accessible to the attacker (authentication is required, but the endpoint is undisclosed)

A user is affected if they are running any of the listed F5 modules in versions 15.1.0-15.1.8, 16.1.0-16.1.3, or 17.1.0 on a multi-bladed system with appliance mode enabled, and the iControl REST API is accessible to authenticated users.

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.9 / 16.1.4 or later
Fixed in 15.1.916.1.4
Interim mitigation

Apply the vendor-provided patch for affected versions; multi-bladed systems in appliance mode should be prioritized given the boundary-crossing capability. Identify and upgrade any EoTS versions to supported releases.

Recommended fix High confidence

Big IP: 15.1.9, 16.1.4, or 17.1.1 (or later). Big IQ: 8.4.0 or latest supported version.

  1. 1. Identify the exact Big IP or Big IQ product, version, and build number currently installed by running 'tmsh show sys version' or checking the web UI status page.
  2. 2. Determine if the system is running in appliance mode (required context for this vulnerability).
  3. 3. For Big IP products: Upgrade to version 15.1.9 or later, 16.1.4 or later, or 17.1.1 or later depending on your current major version branch.
  4. 4. For Big IQ Centralized Management: Upgrade to version 8.4.0 or later if available, or the latest supported version per F5's guidance.
  5. 5. Download the hotfix or update from the F5 Downloads portal (my.f5.com) after authenticating with your F5 account.
  6. 6. Upload the ISO/image to the BIG-IP system via the web UI (System > Software Management > Image List) or tmsh.
  7. 7. Install the new version following F5's standard upgrade procedure: create a new boot location, install the image, and reboot to the new version.
  8. 8. After upgrade, verify the system is running the patched version using 'tmsh show sys version' and confirm the iControl REST endpoint behavior is now secure.
Caveat Upgrading between major versions (e.g., 15.x to 16.x or 16.x to 17.x) may require compatibility review of existing configurations, custom iRules, and integrations. Always test in a non-production environment 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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