dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23020

HIGH · 7.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 16.1.2 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, when the 'Respond on Error' setting is enabled on the Request Logging profile and configured on a 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 · moderate confidence

A denial of service vulnerability exists in F5 BIG-IP 16.1.x before 16.1.2 where the 'Respond on Error' setting in Request Logging profiles, when enabled on a virtual server, allows remote attackers to cause the Traffic Management Microkernel (TMM) to terminate via unspecified requests.

MitigationUpgrade BIG-IP to version 16.1.2 or later, or alternatively disable the 'Respond on Error' setting on affected Request Logging profiles until the upgrade can be performed.

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:>= 16.1.0, < 16.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 16.1.0, < 16.1.2
Big Ip AnalyticsApplication
Affected:>= 16.1.0, < 16.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 16.1.0, < 16.1.2
Big Ip Application Security ManagerApplication
Affected:>= 16.1.0, < 16.1.2
Big Ip Domain Name SystemApplication
Affected:>= 16.1.0, < 16.1.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 16.1.0, < 16.1.2
Big Ip Global Traffic ManagerApplication
Affected:>= 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 the BIG-IP version
    Run `tmsh show sys version` or view the version in the web UI under System > Software Management > Software Images
    Affected if The version is 16.1.0 or 16.1.1 (versions 16.1.2 and later are fixed)
  2. Identify Request Logging profiles
    Run `tmsh list ltm request-log all` to list all Request Logging profiles, or view them in the web UI under Local Traffic > Profiles > Other > Request Logging
    Affected if Any Request Logging profiles exist on the system
  3. Check if Respond on Error is enabled
    For each Request Logging profile, run `tmsh list ltm request-log <profile_name>` and look for the 'respond-with-error' or 'respond on error' setting set to 'enabled'
    Affected if Any profile has 'Respond on Error' or equivalent setting enabled
  4. Identify virtual servers using affected profiles
    Run `tmsh list ltm virtual all` and examine the 'request-log' or 'request-log-profile' field for each virtual server, or check in the web UI under Local Traffic > Virtual Servers
    Affected if Any virtual server has a Request Logging profile with 'Respond on Error' enabled attached to it

You are affected if your BIG-IP version is 16.1.0 or 16.1.1 AND you have a virtual server with a Request Logging profile that has 'Respond on Error' enabled.

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 16.1.2 or later
Fixed in 16.1.2
Interim mitigation

Upgrade BIG-IP to version 16.1.2 or later, or alternatively disable the 'Respond on Error' setting on affected Request Logging profiles until the upgrade can be performed.

Recommended fix High confidence

BIG-IP 16.1.2 or later (including 17.x if supported)

  1. 1. Identify all BIG-IP devices running version 16.1.0 or 16.1.1.
  2. 2. Review virtual servers configured with Request Logging profiles.
  3. 3. If possible, disable the 'Respond on Error' setting on affected Request Logging profiles as a temporary mitigation.
  4. 4. Upgrade BIG-IP to version 16.1.2 or later to resolve the vulnerability.
  5. 5. After upgrade, verify that virtual servers and Request Logging profiles function correctly.
Caveat Review release notes for 16.1.2 for any configuration or behavior changes; test in non-production environment first

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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