dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-23976

MEDIUM · 6.0 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 →
62/100
Remediation priority · Elevated
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 attacker assigned the Administrator role may be able to bypass Appliance mode restrictions utilizing iAppsLX templates on a BIG-IP system.  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 vulnerability allows authenticated administrators on BIG-IP systems running in Appliance mode to bypass Appliance mode security restrictions by leveraging iAppsLX templates. Appliance mode normally restricts administrative capabilities for compliance, but the iAppsLX template functionality provides a pathway to circumvent these restrictions.

MitigationApply the vendor-supplied patch for BIG-IP when available, and review Administrator role assignments and iAppsLX template usage on affected systems until patches can be applied.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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 installed BIG-IP or BIG-IQ version
    Run 'tmsh show /sys version' or check the web UI under Diagnostics > Support. Compare the version number to the affected ranges: 15.1.0 through 15.1.8.x, 16.1.0 through 16.1.3.x, or 17.1.0 for BIG-IP modules; 8.0.0 through 8.3.0 for BIG-IQ.
    Affected if The installed version falls within any of the listed affected version ranges.
  2. Confirm Appliance mode is enabled
    Run 'tmsh show /sys appliance' or check the system configuration for appliance mode status. In the web UI, navigate to System > Platform and look for Appliance mode settings.
    Affected if Appliance mode is currently enabled on the system.
  3. Verify iAppsLX package is installed
    Run 'tmsh list /sys provision' to see provisioned modules, or check the web UI under iApps > Package Management LX to confirm the iAppsLX framework is present.
    Affected if iAppsLX is installed and accessible on the system.
  4. Check for existing iAppsLX templates
    Navigate to iApps > Templates or run 'tmsh list /sys app' to enumerate any deployed iAppsLX application templates.
    Affected if Any iAppsLX templates are present on the system.
  5. Review administrator role assignments
    Check user accounts with administrative privileges via 'tmsh list /auth user' or in the web UI under User Management > Users. Note which accounts have the Administrator role.
    Affected if Multiple administrator accounts exist beyond the primary appliance mode administrator.

A system is affected if it runs a vulnerable BIG-IP or BIG-IQ version, has Appliance mode enabled, and has iAppsLX functionality present, allowing an authenticated administrator to bypass Appliance mode restrictions.

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-supplied patch for BIG-IP when available, and review Administrator role assignments and iAppsLX template usage on affected systems until patches can be applied.

Recommended fix High confidence

BIG-IP 15.1.9+, 16.1.4+, or 17.1.1+ | BIG-IQ 8.4.0+

  1. 1. Identify the exact BIG-IP or BIG-IQ version currently installed by running 'tmsh show sys version' or checking the web UI System > Overview page
  2. 2. For BIG-IP systems: 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
  3. 3. For BIG-IQ systems: Upgrade to version 8.4.0 or later
  4. 4. Download the appropriate upgrade ISO from the F5 Downloads portal (my.f5.com)
  5. 5. Follow F5 upgrade documentation: boot the ISO, verify checksum, and perform the upgrade via Configuration utility or tmsh
  6. 6. After upgrade, verify the new version is running: 'tmsh show sys version'
  7. 7. Test that Appliance mode restrictions are properly enforced after the upgrade
Caveat Review F5 release notes for your target version for potential configuration or compatibility changes; always test in 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
  • 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-23976 — 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-23976 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