dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-22418

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 14.1.5.3 / 15.1.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 versions 17.0.x before 17.0.0.2, 16.1.x before 16.1.3.3, 15.1.x before 15.1.7, 14.1.x before 14.1.5.3, and all versions of 13.1.x, an open redirect vulnerability exists on virtual servers enabled with a BIG-IP APM access policy. This vulnerability allows an unauthenticated malicious attacker to build an open redirect URI. 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

An open redirect vulnerability exists in F5 BIG-IP APM (Access Policy Manager) on virtual servers with APM access policies enabled. An unauthenticated attacker can craft malicious URLs that redirect victims to arbitrary external sites, potentially leading to phishing or credential theft. The vulnerability affects multiple version branches including 13.1.x (all versions), 14.1.x before 14.1.5.3, 15.1.x before 15.1.7, 16.1.x before 16.1.3.3, and 17.0.x before 17.0.0.2.

MitigationUpgrade BIG-IP to the patched versions (17.0.0.2, 16.1.3.3, 15.1.7, or 14.1.5.3 or later). Note that 13.1.x has no patch and reached EoTS, so migration to a supported version is required.

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>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, <= 13.1.5>= 15.1.0, < 15.1.7>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 product version
    Run `tmsh show sys version` or inspect /etc/product_version on the BIG-IP device
    Affected if The version falls within 13.1.0-13.1.5, 14.1.0-14.1.5.2, 15.1.0-15.1.6, 16.1.0-16.1.3.2, or 17.0.0-17.0.0.1
  2. Verify APM module provisioning
    Run `tmsh show sys provision` and look for apm in the output
    Affected if APM shows as provisioned (any capacity level)
  3. Identify virtual servers with APM access policies
    Run `tmsh list ltm virtual all-properties` and inspect the apm-policy-agent or access-policy setting for each virtual server
    Affected if Any virtual server has an APM access-policy explicitly assigned (not set to none)
  4. Confirm the specific vulnerable configuration
    Review the access policy associated with affected virtual servers - the vulnerability triggers on the APM login page redirect parameter
    Affected if A virtual server has an APM access policy enabled and the BIG-IP version is in the affected range listed above

A user is affected if their BIG-IP runs a version in the affected ranges AND has at least one virtual server with an APM access policy assigned.

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 / 15.1.7 / 16.1.3.3 or later
Fixed in 14.1.5.315.1.716.1.3.3
Interim mitigation

Upgrade BIG-IP to the patched versions (17.0.0.2, 16.1.3.3, 15.1.7, or 14.1.5.3 or later). Note that 13.1.x has no patch and reached EoTS, so migration to a supported version is required.

Recommended fix High confidence

Upgrade to 14.1.5.3 (for 14.1.x), 15.1.7 (for 15.1.x), 16.1.3.3 (for 16.1.x), or 17.0.0.2 (for 17.0.x). Version 13.1.x has EoTS and requires upgrade to a supported release.

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI footer.
  2. 2. Determine which BIG-IP module(s) are affected (APM, AFM, Analytics, AAM, ASM, DDoS Hybrid Defender, DNS, or FPS).
  3. 3. For BIG-IP versions 13.1.x: These versions have reached End of Technical Support (EoTS). F5 recommends upgrading to a supported release as there is no patch available.
  4. 4. For BIG-IP versions 14.1.0-14.1.5.3: Upgrade to version 14.1.5.3 or later.
  5. 5. For BIG-IP versions 15.1.0-15.1.7: Upgrade to version 15.1.7 or later.
  6. 6. For BIG-IP versions 16.1.0-16.1.3.3: Upgrade to version 16.1.3.3 or later.
  7. 7. For BIG-IP versions 17.0.0-17.0.0.2: Upgrade to version 17.0.0.2 or later.
  8. 8. After upgrade, verify the BIG-IP APM access policy configuration on affected virtual servers to ensure the vulnerability is remediated.
Caveat Review F5 release notes for each target version for potential configuration or behavioral changes. Upgrading across major versions (e.g., 13.1 to 17.0) may require more extensive testing.

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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