dbcve.org
Big Ip Advanced Firewall ManagerApplication · F5

CVE-2022-23024

HIGH · 7.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to after 15.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 · unedited
On BIG-IP AFM version 16.x before 16.1.0, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.2, and all versions of 13.1.x, when the IPsec application layer gateway (ALG) logging profile is configured on an IPsec ALG virtual server, undisclosed IPsec 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 · high confidence

Denial of service vulnerability in BIG-IP AFM's IPsec Application Layer Gateway (ALG). When the IPsec ALG logging profile is configured on an IPsec ALG virtual server, specific undisclosed IPsec traffic triggers a condition causing the Traffic Management Microkernel (TMM) to terminate, resulting in service disruption.

MitigationUpgrade to BIG-IP version 16.1.0, 15.1.4.1, 14.1.4.2 or later. Alternatively, if immediate upgrade is not feasible, disable the IPsec ALG logging profile on affected virtual servers as a temporary workaround.

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 Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4.1>= 15.1.0, <= 15.1.4

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

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. Verify BIG-IP version is within affected ranges
    Run 'tmsh show sys version' or check the web UI under Dashboard > General to obtain the installed BIG-IP version. Compare it against these affected ranges: 13.1.0-13.1.4, 14.1.0-14.1.4.1, or 15.1.0-15.1.4
    Affected if The installed version falls within any of these ranges
  2. Confirm BIG-IP AFM module is provisioned
    Run 'tmsh show sys provision' or check under System > Platform > Provisioning in the web UI. Verify that AFM (Advanced Firewall Manager) is provisioned
    Affected if AFM module is provisioned at any level
  3. Identify IPsec ALG virtual servers
    Run 'tmsh list ltm virtual all' and look for virtual servers with profile type ipsec-alg, or inspect via the web UI under Local Traffic > Virtual Servers
    Affected if Any virtual server is configured with an IPsec ALG profile
  4. Check for IPsec ALG logging profile attachment
    Run 'tmsh list ltm virtual <virtual_name>' for each IPsec ALG virtual server and inspect the 'alg-log-profile' or logging configuration, or view via the web UI under the virtual server properties
    Affected if An IPsec ALG logging profile is attached to any IPsec ALG virtual server

The environment is affected if BIG-IP is running an affected version (13.1.x, 14.1.0-14.1.4.1, or 15.1.0-15.1.4), AFM module is provisioned, and an IPsec ALG virtual server has an IPsec ALG logging profile enabled.

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 a release after 15.1.4
Interim mitigation

Upgrade to BIG-IP version 16.1.0, 15.1.4.1, 14.1.4.2 or later. Alternatively, if immediate upgrade is not feasible, disable the IPsec ALG logging profile on affected virtual servers as a temporary workaround.

Recommended fix High confidence

For 14.1.x: upgrade to 14.1.4.2; For 15.1.x: upgrade to 15.1.4.1; For 16.x: upgrade to 16.1.0 or later; Note: 13.1.x has no fix available and is End of Technical Support

  1. 1. Back up the BIG-IP configuration using the command: tmsh save sys config all-partitions
  2. 2. Schedule a maintenance window as the upgrade may cause brief service interruptions
  3. 3. Download the appropriate hotfix from the F5 download page (search for K60212041 or the specific version): For 14.1.x upgrade to 14.1.4.2, for 15.1.x upgrade to 15.1.4.1, for 16.x upgrade to 16.1.0 or later
  4. 4. Upload the ISO image to the BIG-IP via WebUI (System > Software Management > Image List) or via tmsh: tmsh install sys software image <filename> volume <volume-name>
  5. 5. Install the image and reboot: tmsh install sys software volume <volume-name> boot-image <image-name>
  6. 6. After reboot, verify the version: tmsh show sys version
  7. 7. Verify the IPsec ALG virtual server is functioning correctly and TMM is stable
Caveat 13.1.x has no fix available and is End of Technical Support - consider migrating to a supported version; Always test upgrades in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Advanced Firewall Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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