dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2024-22389

HIGH · 7.2 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 →
78/100
Remediation priority · High
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 BIG-IP is deployed in high availability (HA) and an iControl REST API token is updated, the change does not sync to the peer device. 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 · high confidence

In BIG-IP HA deployments, when an iControl REST API token is updated via the API, the token change fails to synchronize to the peer device. This creates an inconsistency where one device has the new token while the peer retains the old one, potentially causing authentication failures, API call issues, or improper failover behavior.

MitigationForce synchronization between HA peers after token updates, or manually update tokens on both devices. Consult F5 documentation for HA sync configuration settings and ensure the sync group is properly configured for iControl REST objects.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Confirm HA deployment is in use
    Check if the device is part of an HA pair by running 'tmsh show sys ha' or reviewing the HA status in the web UI under Device Management > Devices. This vulnerability only affects HA environments.
    Affected if HA is not configured, the vulnerability does not apply.
  2. Identify the installed product version
    Run 'tmsh show sys version' for Big-IP or check the Big-IQ version under System > Software Management > Images. Compare the version number to the affected ranges: 15.1.0-15.1.8, 16.1.0-16.1.3, 17.1.0 for Big-IP; 8.0.0-8.3.0 for Big-IQ.
    Affected if The version falls within any of the affected ranges listed in the CVE.
  3. Verify iControl REST API token synchronization
    Compare the iControl REST authentication token state between HA peers. Log into each device separately via iControl REST and query /mgmt/shared/authz/tokens or review the token creation timestamps. Alternatively, trigger a token update via API on one device and verify it propagates to the peer.
    Affected if One device shows a newer token while the peer retains an older token, indicating sync failure.
  4. Check for authentication failures in logs
    Review /var/log/restnoded.log on both HA peers for authentication failure events or API call errors that coincide with token update times. Search for patterns like 'authentication failed' or 'token not found' around recent API operations.
    Affected if Authentication failures occur on one peer but not the other after token updates, suggesting token desynchronization.

You are affected if HA is configured, the product version falls within the affected ranges, and token synchronization has failed between HA peers as evidenced by mismatched token state or one-sided authentication failures.

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

Force synchronization between HA peers after token updates, or manually update tokens on both devices. Consult F5 documentation for HA sync configuration settings and ensure the sync group is properly configured for iControl REST objects.

Recommended fix High confidence

BIG-IP 15.1.9, 16.1.4, or 17.1.1 (or later stable releases); BIG-IQ 8.4.0 or later

  1. 1. Identify the current BIG-IP/BIG-IQ version by running 'tmsh show sys version' or checking the web UI.
  2. 2. Schedule a maintenance window for the upgrade process.
  3. 3. For HA configurations, back up the current configuration using 'tmsh save sys config' and verify synchronization between peer devices.
  4. 4. Download the appropriate fixed version from F5 Networks (15.1.9, 16.1.4, or 17.1.1 for the respective product).
  5. 5. Upload the ISO/image to the BIG-IP/BIG-IQ system via the web UI (System > Software Management > Image List) or API.
  6. 6. For HA pairs, upgrade the standby/peer device first using the volume install option.
  7. 7. Verify the upgrade completed successfully and the system is stable.
  8. 8. Force a config sync between HA peers using 'tmsh run sys config-sync' to ensure configuration consistency.
Caveat Review F5 release notes for any configuration or behavior changes between versions; 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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