dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23019

HIGH · 7.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 14.1.4.4 / 15.1.4.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.2, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.4, and all versions of 13.1.x and 12.1.x, when a message routing type virtual server is configured with both Diameter Session and Router Profiles, undisclosed traffic can cause an increase in memory resource utilization. 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 · moderate confidence

A memory resource exhaustion vulnerability in F5 BIG-IP allows undisclosed traffic to cause increased memory utilization when a message routing type virtual server is configured with both Diameter Session and Router profiles. The vulnerability has a CVSS score of 7.5 (HIGH) due to the potential for denial of service through memory exhaustion.

MitigationApply the vendor-supplied patches for affected versions (16.1.2, 15.1.4.1, 14.1.4.4) or identify and reconfigure affected virtual servers to remove the problematic Diameter Session/Router profile combination if patching is not feasible.

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:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, < 16.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, < 16.1.2
Big Ip AnalyticsApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, < 16.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, < 16.1.2
Big Ip Application Security ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, < 16.1.2
Big Ip Domain Name SystemApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, <= 16.1.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, < 16.1.2
Big Ip Global Traffic ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.1.0, <= 16.1.2

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 view System > Dashboard in the web UI to identify the installed version
    Affected if The installed version falls within: 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4.3, 15.1.0-15.1.4.0, or 16.1.0-16.1.1
  2. Identify message routing virtual servers
    Run 'tmsh list /ltm virtual all-properties' and look for entries where 'type' is set to 'message-routing'
    Affected if Any virtual server is configured with type message-routing
  3. Check for Diameter Session profile
    For each message-routing virtual server, inspect the profiles section using 'tmsh list /ltm virtual vsname profiles' and look for a profile named 'diameter-session' or a diameter-session type profile
    Affected if The virtual server has a Diameter Session profile assigned
  4. Check for Diameter Router profile
    For each message-routing virtual server, inspect the profiles section and look for a profile named 'diameter-router' or a diameter router type profile
    Affected if The virtual server has a Diameter Router profile assigned
  5. Confirm vulnerable configuration
    If both Diameter Session and Diameter Router profiles are present on the same message-routing virtual server, the environment is vulnerable
    Affected if Both profiles are simultaneously enabled on a message-routing type virtual server

The environment is affected if the BIG-IP version is within the affected ranges AND a message-routing virtual server has both Diameter Session and Router profiles configured together.

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.4.4 / 15.1.4.1 / 16.1.2 or later
Fixed in 14.1.4.415.1.4.116.1.2
Interim mitigation

Apply the vendor-supplied patches for affected versions (16.1.2, 15.1.4.1, 14.1.4.4) or identify and reconfigure affected virtual servers to remove the problematic Diameter Session/Router profile combination if patching is not feasible.

Recommended fix High confidence

Upgrade to BIG-IP 14.1.4.4, 15.1.4.1, or 16.1.2 (or later) depending on your current major version branch

  1. 1. Identify the current BIG-IP version by checking the system information in the web management interface or running 'tmsh show sys version' on the command line.
  2. 2. Determine if a message routing type virtual server is configured with both Diameter Session and Diameter Router profiles, as this is the specific configuration that triggers the vulnerability.
  3. 3. Schedule a maintenance window for the upgrade, as this will require a system reboot.
  4. 4. Back up the current BIG-IP configuration using 'tmsh save sys config' or the web management interface.
  5. 5. Download the appropriate fixed version from F5 Networks (14.1.4.4, 15.1.4.1, or 16.1.2 or later) from support.f5.com.
  6. 6. Upload the ISO image to the BIG-IP system via the web interface (System > Software Management > Image List) or via SCP/tftp.
  7. 7. Install the new version using the BIG-IP web interface (System > Software Management > Volume List) or via tmsh: 'install sys software volume <volume_name> <image_name>'.
  8. 8. Activate the new volume and reboot the system to complete the upgrade.
Caveat Versions 12.1.x and 13.1.x have reached End of Technical Support (EoTS) and no patch is available; only upgrade path is to move to 14.1.x, 15.1.x, or 16.1.x

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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