dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23025

HIGH · 7.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to after 16.1.1 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 version 16.1.x before 16.1.1, 15.1.x before 15.1.4, 14.1.x before 14.1.4.4, and all versions of 13.1.x, when a SIP ALG profile is configured on a virtual server, undisclosed requests 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

This is a denial-of-service vulnerability in F5 BIG-IP's SIP ALG (Session Initiation Protocol Application Layer Gateway) functionality. When a SIP ALG profile is configured on a virtual server, specially crafted SIP requests can cause the Traffic Management Microkernel (TMM) to terminate, resulting in service disruption.

MitigationUpgrade BIG-IP to version 16.1.1 or later (16.1.x), 15.1.4 or later (15.1.x), or 14.1.4.4 or later (14.1.x). For 13.1.x versions, upgrade to a supported version as all 13.1.x versions are affected.

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:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip Advanced Web Application FirewallApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3>= 16.1.0, <= 16.1.1

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. Identify the BIG-IP version
    Run `tmsh show /sys version` or check the web UI under System > Software Management > Software Images to find the installed version.
    Affected if The installed version is 13.1.0-13.1.4, 14.1.0-14.1.4, 15.1.0-15.1.3, or 16.1.0-16.1.1.
  2. List configured SIP ALG profiles
    Run `tmsh list /ltm sip profile` to see if any SIP profiles exist on the system.
    Affected if Any SIP profile is listed in the output.
  3. Check virtual servers using SIP profiles
    Run `tmsh list /ltm virtual all` and look for a sip-profile reference in the virtual server configuration.
    Affected if A virtual server references a SIP profile in its configuration.

You are affected if your BIG-IP version falls within the listed vulnerable ranges AND a SIP ALG profile is actively attached to a virtual server.

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 16.1.1
Interim mitigation

Upgrade BIG-IP to version 16.1.1 or later (16.1.x), 15.1.4 or later (15.1.x), or 14.1.4.4 or later (14.1.x). For 13.1.x versions, upgrade to a supported version as all 13.1.x versions are affected.

Recommended fix High confidence

Upgrade to BIG-IP 16.1.1 (or later 16.1.x), 15.1.4 (or later 15.1.x), or 14.1.4.4 (or later 14.1.x). Note: 13.1.x is End of Technical Support and has no fix; migrate to a supported version.

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI at System > Software > Image List
  2. 2. Identify if SIP ALG profile is configured on any virtual servers by reviewing the virtual server configuration or running 'tmsh list lsnap virtual'
  3. 3. Schedule a maintenance window for the upgrade, ensuring backup of the configuration
  4. 4. Download the appropriate fixed version from F5 Networks (16.1.1, 15.1.4, or 14.1.4.4 or later)
  5. 5. Upload the ISO image to the BIG-IP and install via 'tmsh install sys software' or the web UI at System > Software > Image List > Install
  6. 6. Reboot the device to load the new version
  7. 7. Verify the upgrade by running 'tmsh show sys version' and confirm the new version is active
  8. 8. After upgrade, verify virtual servers and SIP ALG profiles are functioning correctly
Caveat Upgrading BIG-IP versions may introduce compatibility issues with existing configurations or integrations; always test in a staging environment first. The 13.1.x branch has reached End of Technical Support and no patch is available.

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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