dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-26370

HIGH · 7.5 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 F5 BIG-IP 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5, and 14.1.x versions prior to 14.1.4.6, when a Session Initiation Protocol (SIP) message routing framework (MRF) application layer gateway (ALG) profile is configured on a Message Routing 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 Session Initiation Protocol (SIP) Message Routing Framework (MRF) Application Layer Gateway (ALG). When a SIP MRF ALG profile is configured on a Message Routing virtual server, specially crafted undisclosed SIP requests can cause the Traffic Management Microkernel (TMM) to terminate, resulting in disruption of traffic processing for all virtual servers on the affected device.

MitigationUpgrade to BIG-IP versions 16.1.2.2, 15.1.5, or 14.1.4.6 or later. If upgrading is not immediately feasible, review and disable the SIP ALG profile on Message Routing virtual servers if not required for business operations.

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:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip AnalyticsApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Application Acceleration ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Application Security ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Domain Name SystemApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Fraud Protection ServiceApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Global Traffic ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 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. Determine the installed BIG-IP version
    Run 'tmsh show sys version' or check the BIG-IP web UI under System > Software Management > Image List to view the installed version.
    Affected if The version matches one of the affected versions: 14.1.0, 14.1.2, 14.1.3, 14.1.4, 15.1.0 through 15.1.5, or 16.1.0 through 16.1.1
  2. Identify Message Routing virtual servers
    Run 'tmsh list ltm virtual all' and look for virtual servers with type 'message-routing' or check the web UI under Local Traffic > Virtual Servers for virtual servers configured with Message Routing profile.
    Affected if A Message Routing virtual server exists on the device
  3. Check for SIP MRF ALG profile configuration
    Run 'tmsh list ltm sip profile' to list all SIP profiles, then run 'tmsh list ltm virtual <name>' for each Message Routing virtual server to inspect the sip-profile setting.
    Affected if A SIP MRF ALG profile is assigned to a Message Routing virtual server
  4. Verify SIP ALG feature is enabled
    Examine the SIP profile configuration with 'tmsh list ltm sip profile <profile_name>' and check if the ALG mode is enabled, or inspect the virtual server profile configuration for SIP ALG settings.
    Affected if The SIP MRF ALG feature is explicitly enabled in the profile or virtual server configuration

You are affected if your BIG-IP version is one of the listed affected versions AND a SIP MRF ALG profile is actively configured on a Message Routing 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to BIG-IP versions 16.1.2.2, 15.1.5, or 14.1.4.6 or later. If upgrading is not immediately feasible, review and disable the SIP ALG profile on Message Routing virtual servers if not required for business operations.

Recommended fix High confidence

14.1.4.6 (or later; also fixed in 15.1.5 and 16.1.2.2 for respective branches)

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI
  2. 2. Download BIG-IP version 14.1.4.6 (or a later fixed version) from the F5 downloads portal at support.f5.com
  3. 3. Back up the current BIG-IP configuration using 'tmsh save sys config' or the web UI backup feature
  4. 4. Upload the ISO image to the BIG-IP and install the update via the web UI (System > Software Management > ISO Image) or using 'tmsh install sys software'
  5. 5. After installation, reboot the device to load the new version
  6. 6. Verify the upgrade was successful by checking 'tmsh show sys version' and confirming the version shows 14.1.4.6 or later
  7. 7. Test that the SIP MRF ALG profile functions correctly and the TMM no longer terminates on the affected virtual servers

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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