dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23027

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to after 15.1.3 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 versions 15.1.x before 15.1.4, 14.1.x before 14.1.4.4, 13.1.x beginning in 13.1.3.6, 12.1.5.3-12.1.6, and 11.6.5.2, when a FastL4 profile and an HTTP, FIX, and/or hash persistence profile are configured on the same virtual server, undisclosed requests can cause the virtual server to stop processing new client connections. 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 where specific profile combinations (FastL4 with HTTP, FIX, and/or hash persistence profiles on the same virtual server) cause the virtual server to stop processing new client connections when receiving undisclosed requests.

MitigationUpgrade BIG-IP to version 15.1.4, 14.1.4.4, or later; alternatively, reconfigure virtual servers to remove the problematic profile combination if upgrading 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.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip Advanced Web Application FirewallApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip AnalyticsApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip Application Security ManagerApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.3
Big Ip Domain Name SystemApplication
Affected:>= 12.1.5.3, <= 12.1.6>= 13.1.3.6, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.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
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. Check BIG-IP version
    Run 'tmsh show /sys version' or 'bigstart version' to obtain the installed version
    Affected if Version is 12.1.5.3-12.1.6, 13.1.3.6-13.1.4, 14.1.0-14.1.4, or 15.1.0-15.1.3
  2. Identify FastL4 virtual servers
    Run 'tmsh list /ltm virtual one-line' and look for virtual servers that reference a FastL4 profile in their 'profile' or 'profiles' section
    Affected if Any virtual server uses a FastL4 profile (usually named 'fastL4' or similar)
  3. Check for HTTP profile on FastL4 virtual servers
    For each FastL4 virtual server identified, run 'tmsh list /ltm virtual <vs_name>' and examine the profiles list for an HTTP profile (profile http)
    Affected if The same virtual server has both a FastL4 profile and an HTTP profile enabled simultaneously
  4. Check for FIX profile on FastL4 virtual servers
    Examine the profiles list for each FastL4 virtual server and look for a FIX profile (profile fix)
    Affected if The same virtual server has both a FastL4 profile and a FIX profile enabled simultaneously
  5. Check for hash persistence profile on FastL4 virtual servers
    Examine the profiles list for each FastL4 virtual server and look for hash-based persistence profiles such as 'hash', 'dest_addr', or 'source_addr' persistence
    Affected if The same virtual server has both a FastL4 profile and any hash-based persistence profile enabled simultaneously

Your environment is affected if you run a vulnerable BIG-IP version AND have virtual servers configured with a FastL4 profile combined with HTTP, FIX, or hash persistence profiles on the same 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 15.1.3
Interim mitigation

Upgrade BIG-IP to version 15.1.4, 14.1.4.4, or later; alternatively, reconfigure virtual servers to remove the problematic profile combination if upgrading is not feasible.

Recommended fix High confidence

15.1.4 or later (or 14.1.4.4+ or 13.1.5+ depending on current branch)

  1. 1. Back up the current BIG-IP configuration using the Backup/Restore functionality or by exporting UCS files.
  2. 2. Identify all virtual servers that have both a FastL4 profile and an HTTP, FIX, or hash persistence profile configured.
  3. 3. Consult F5 BIG-IP release notes and upgrade to a fixed version: 15.1.4 or later, 14.1.4.4 or later, or 13.1.5 or later (depending on your current major version).
  4. 4. After upgrade, verify the BIG-IP version matches the expected fixed release using 'tmsh show sys version'.
  5. 5. Restore the configuration from the backup if not automatically preserved.
  6. 6. Test that the affected virtual servers accept new client connections and handle traffic normally.
  7. 7. Monitor for any recurrence of the denial-of-service condition.
Caveat Upgrading BIG-IP may introduce compatibility changes; ensure review of release notes for any impacts to custom iRules, profiles, or integrated applications

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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