dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-22842

HIGH · 7.5 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 14.1.5.3 / 15.1.8.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 versions 16.1.x before 16.1.3.3, 15.1.x before 15.1.8.1, 14.1.x before 14.1.5.3, and all versions of 13.1.x, when a SIP profile is configured on a Message Routing type virtual server, undisclosed 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

A denial of service vulnerability in BIG-IP TMM where specially crafted traffic directed at a Message Routing virtual server with an active SIP profile causes the Traffic Management Microkernel to terminate, resulting in service disruption.

MitigationUpgrade BIG-IP to version 16.1.3.3 or later (15.1.x to 15.1.8.1+, 14.1.x to 14.1.5.3+). For 13.1.x (EoTS), remove or disable SIP profiles from Message Routing virtual servers as no patch is available.

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.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8.1>= 16.1.0, < 16.1.3.3

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. Check BIG-IP version
    Run 'tmsh show sys version' or inspect /etc/product_version to obtain the installed BIG-IP version
    Affected if The version falls within these ranges: 13.1.0-13.1.5, 14.1.0-14.1.5.2, 15.1.0-15.1.8.0, or 16.1.0-16.1.3.2
  2. Identify Message Routing virtual servers
    Run 'tmsh list ltm virtual' and look for virtual servers with 'profile' entries containing 'sip' or 'message-routing'
    Affected if Any virtual server is configured with a Message Routing profile type
  3. Verify SIP profile is attached
    For each Message Routing virtual server, run 'tmsh list ltm virtual <name>' and examine the 'profile' section for a sip profile
    Affected if A SIP profile is listed in the virtual server's profile configuration
  4. Confirm TMM restart events
    Check /var/log/ltm for TMM crash events or run 'tmsh show sys tmm-stat' for abnormal restart counts
    Affected if Multiple TMM restarts have occurred without corresponding maintenance windows

You are affected if your BIG-IP version is in the vulnerable range AND you have a Message Routing virtual server with an active SIP profile configured.

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 14.1.5.3 / 15.1.8.1 / 16.1.3.3 or later
Fixed in 14.1.5.315.1.8.116.1.3.3
Interim mitigation

Upgrade BIG-IP to version 16.1.3.3 or later (15.1.x to 15.1.8.1+, 14.1.x to 14.1.5.3+). For 13.1.x (EoTS), remove or disable SIP profiles from Message Routing virtual servers as no patch is available.

Recommended fix High confidence

14.1.5.3 or later; 15.1.8.1 or later; 16.1.3.3 or later (13.1.x is EoTS with no fix)

  1. 1. Identify the current BIG-IP version by checking System > Software Management > ISO Image or using 'tmsh show sys version'
  2. 2. Determine if a SIP profile is configured on any Message Routing type virtual servers (Go to Local Traffic > Virtual Servers > Virtual Server List and review profiles)
  3. 3. If SIP profiles are in use on Message Routing virtual servers, plan for immediate upgrade due to the severity of TMM termination
  4. 4. For BIG-IP 14.1.x: Upgrade to version 14.1.5.3 or later
  5. 5. For BIG-IP 15.1.x: Upgrade to version 15.1.8.1 or later
  6. 6. For BIG-IP 16.1.x: Upgrade to version 16.1.3.3 or later
  7. 7. For BIG-IP 13.1.x: This version is End of Technical Support (EoTS) with no patch available; migrate to a supported version (14.1.5.3+, 15.1.8.1+, or 16.1.3.3+)
  8. 8. After upgrade, verify virtual servers are operational and TMM is stable
Caveat Upgrading across major version branches may require compatibility review; 13.1.x has reached End of Technical Support and requires migration to a supported version

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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