Big Ip Access Policy ManagerApplication · F5

CVE-2023-22341

HIGH · 7.5 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 14.1.5.3 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 version 14.1.x before 14.1.5.3, and all versions of 13.1.x, when the BIG-IP APM system is configured with all the following elements, undisclosed requests may cause the Traffic Management Microkernel (TMM) to terminate: * An OAuth Server that references an OAuth Provider * An OAuth profile with the Authorization Endpoint set to '/' * An access profile that references the above OAuth profile and is associated with an HTTPS virtual server 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 APM where specific OAuth configurations can cause the Traffic Management Microkernel (TMM) to terminate. The vulnerability requires a precise setup: an OAuth Server referencing an OAuth Provider, an OAuth profile with Authorization Endpoint set to '/', an access profile using that OAuth profile, and an HTTPS virtual server. When these conditions align, undisclosed requests trigger TMM termination.

MitigationUpgrade BIG-IP to version 14.1.5.3 or later (14.2.x), or modify the OAuth profile configuration to change the Authorization Endpoint from '/' to a valid path.

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

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 confirm the installed version falls within 13.1.0-13.1.5 or 14.1.0-14.1.5.2
    Affected if Version is 13.1.0 through 13.1.5, or 14.1.0 through 14.1.5.2
  2. Verify APM module is provisioned
    Run 'tmsh show sys provision' or check /config/bigip.license to see if apm is provisioned
    Affected if APM module is provisioned and running
  3. Identify OAuth Server objects
    Navigate to Access Policy Manager > OAuth Server in the GUI, or run 'tmsh list apm oauth server' to list all OAuth Server configurations
    Affected if OAuth Server objects exist referencing an OAuth Provider
  4. Inspect OAuth profile Authorization Endpoint
    Run 'tmsh list apm oauth profile' and check each profile's 'authorization-endpoint' setting
    Affected if Any OAuth profile has authorization-endpoint set to '/' (a forward slash)
  5. Verify access profile uses OAuth profile
    Run 'tmsh list apm profile access' and check the 'oauth-profile' setting within each access profile
    Affected if An access profile references an OAuth profile with authorization-endpoint set to '/'
  6. Confirm HTTPS virtual server exists
    Run 'tmsh list ltm virtual' and check for a virtual server with destination using HTTPS port 443
    Affected if An HTTPS virtual server exists and is associated with the access profile from the previous step

The environment is affected if BIG-IP runs a vulnerable version (13.1.0-13.1.5 or 14.1.0-14.1.5.2), APM is provisioned, and the specific OAuth chain exists: OAuth Server -> OAuth profile with Authorization Endpoint '/' -> Access profile -> HTTPS 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 14.1.5.3 or later
Fixed in 14.1.5.3
Interim mitigation

Upgrade BIG-IP to version 14.1.5.3 or later (14.2.x), or modify the OAuth profile configuration to change the Authorization Endpoint from '/' to a valid path.

Recommended fix High confidence

14.1.5.3 or later (14.1.x stable)

  1. 1. Identify the current BIG-IP APM version using 'tmsh show sys version' or the web management console.
  2. 2. If running 14.1.x versions before 14.1.5.3, upgrade to version 14.1.5.3 or later.
  3. 3. If running any 13.1.x version, note that 13.1.x has reached End of Technical Support (EoTS); consider upgrading to a supported version such as 14.1.5.3+ or the latest 15.x/16.x stable release.
  4. 4. After upgrade, verify the OAuth Server, OAuth Provider, and OAuth profile configurations to ensure Authorization Endpoint is not set to '/' unless required for business logic.
  5. 5. Test the Access Policy Manager functionality after upgrade to confirm normal operation.
Caveat Upgrading between major versions may require compatibility testing of existing access policies and OAuth configurations; 13.1.x is EoTS and receives no further security patches

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-2023-22341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-22341 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