dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23029

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to after 15.1.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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.x before 16.1.0, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.4, and all versions of 13.1.x, 12.1.x, and 11.6.x, when a FastL4 profile is configured on a virtual server, 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

When a FastL4 (Fast Layer 4) profile is configured on a BIG-IP virtual server, certain undisclosed traffic patterns can cause excessive memory consumption, potentially leading to memory exhaustion and denial of service.

MitigationUpgrade BIG-IP to version 16.1.0, 15.1.4.1, or 14.1.4.4 or later. For EoTS versions (13.1.x, 12.1.x, 11.6.x), consider migrating to a supported version or implement traffic filtering upstream.

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:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip Advanced Web Application FirewallApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip AnalyticsApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip Application Security ManagerApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4
Big Ip Domain Name SystemApplication
Affected:>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 BIG-IP version
    Run 'tmsh show sys version' or check the BIG-IP GUI under System > Software > Volume. Compare the installed version against the affected ranges: 11.6.1-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4, 15.1.0-15.1.4
    Affected if Installed version falls within any of the listed vulnerable ranges
  2. Locate virtual servers with FastL4 profile
    Run 'tmsh list ltm virtual profile' or access the BIG-IP GUI under Local Traffic > Virtual Servers. Examine each virtual server configuration to identify which ones have a FastL4 (Fast Layer 4) profile applied
    Affected if Any virtual server is configured with a FastL4 profile
  3. Verify FastL4 profile type
    For each virtual server with a FastL4 profile, run 'tmsh list ltm profile fastl4 <profile_name>' to confirm the profile type is FastL4
    Affected if A FastL4 profile object exists and is assigned to a virtual server
  4. Confirm traffic exposure
    Review virtual server logs and traffic statistics to determine if the affected virtual servers are exposed to external or untrusted traffic patterns
    Affected if The virtual server with FastL4 profile is processing traffic from network sources that could trigger the memory exhaustion condition

User is affected if BIG-IP version falls within 11.6.1-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4, or 15.1.0-15.1.4 AND a FastL4 profile is configured on any virtual server that handles traffic

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 BIG-IP to version 16.1.0, 15.1.4.1, or 14.1.4.4 or later. For EoTS versions (13.1.x, 12.1.x, 11.6.x), consider migrating to a supported version or implement traffic filtering upstream.

Recommended fix High confidence

Upgrade to 14.1.4.4+ (14.1.x branch), 15.1.4.1+ (15.1.x branch), or 16.1.0+ (16.x branch)

  1. Identify all BIG-IP devices running affected versions (11.6.x, 12.1.x, 13.1.x, 14.1.0-14.1.4, 15.1.0-15.1.4.0, 16.0.x)
  2. Determine which virtual servers have FastL4 profiles configured
  3. For BIG-IP version 14.1.x: upgrade to 14.1.4.4 or later
  4. For BIG-IP version 15.1.x: upgrade to 15.1.4.1 or later
  5. For BIG-IP version 16.x: upgrade to 16.1.0 or later
  6. After upgrade, verify FastL4 profiles are functioning correctly and monitor memory utilization
  7. Note: Versions 11.6.x, 12.1.x, and 13.1.x have reached End of Technical Support and do not receive security patches; upgrade to a supported version branch
Caveat Versions 11.6.x, 12.1.x, and 13.1.x are End of Technical Support and require full version upgrade to a supported branch; ensure compatibility testing before upgrading in production

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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