dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-41373

CRITICAL · 9.9 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to 14.1.5.6 / 15.1.10.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
A directory traversal vulnerability exists in the BIG-IP Configuration Utility that may allow an authenticated attacker to execute commands on the BIG-IP system. For BIG-IP system running in Appliance mode, a successful exploit can allow the attacker to cross a security boundary.  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

A directory traversal vulnerability in BIG-IP Configuration Utility allows authenticated attackers to escape intended directory constraints and execute arbitrary system commands. In Appliance mode deployments, successful exploitation enables the attacker to cross security boundaries, potentially compromising the entire system.

MitigationApply the applicable F5 security update or hotfix for this vulnerability. Restrict access to the Configuration Utility to trusted administrative users only and follow F5's Appliance mode security guidelines.

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.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip Local Traffic ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip Advanced Web Application FirewallApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.6>= 15.1.0, < 15.1.10.2>= 16.1.0, < 16.1.4.1>= 17.1.0, < 17.1.0.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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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. Identify installed BIG-IP modules and versions
    Run 'tmsh show /sys version' or 'tmsh list /sys software' to see installed modules and their versions
    Affected if Any module version falls within: 13.1.0-13.1.5, 14.1.0-14.1.5.5, 15.1.0-15.1.10.1, 16.1.0-16.1.4.0, or 17.1.0-17.1.0.2
  2. Verify Configuration Utility status
    Check if the Configuration Utility (web management interface) is enabled and accessible. Run 'tmsh list /sys httpd' or check via the web UI under System > Configuration > Device Management > HTTPd Properties
    Affected if The Configuration Utility is enabled and listening on the management interface or a VLAN
  3. Confirm authentication method for Config Utility
    Review the access profile for the Configuration Utility. Check 'tmsh list /sys httpd' for 'auth' settings and verify whether local user accounts, remote authentication (RADIUS, LDAP, or TACACS+), or SAML is in use
    Affected if User authentication to the Configuration Utility is possible (even with low-privileged accounts)
  4. Check if Appliance mode is enabled
    Run 'tmsh list /sys global-settings' and look for 'appliance' or 'security' settings. In the web UI, check System > Configuration > Security > Appliance Settings
    Affected if Appliance mode restrictions are in place, as exploitation in this mode allows crossing security boundaries

You are affected if your BIG-IP system runs any of the listed modules in the affected version ranges AND the Configuration Utility is accessible to authenticated users.

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.6 / 15.1.10.2 / 16.1.4.1 or later
Fixed in 14.1.5.615.1.10.216.1.4.1
Interim mitigation

Apply the applicable F5 security update or hotfix for this vulnerability. Restrict access to the Configuration Utility to trusted administrative users only and follow F5's Appliance mode security guidelines.

Recommended fix High confidence

Upgrade to the following fixed releases: 14.1.5.6+, 15.1.10.2+, or 16.1.4.1+ (depending on your major version branch). Version 13.1.x has EoTS and requires migration to a supported branch.

  1. 1. Identify the currently installed BIG-IP version by running 'tmsh show sys version' or checking the Configuration Utility version information.
  2. 2. Determine which BIG-IP module(s) (APM, AFM, ASM, DNS, LTM, AWA, Analytics, AAM) are affected on your system.
  3. 3. For BIG-IP versions 14.1.x: Upgrade to version 14.1.5.6 or later.
  4. 4. For BIG-IP versions 15.1.x: Upgrade to version 15.1.10.2 or later.
  5. 5. For BIG-IP versions 16.1.x: Upgrade to version 16.1.4.1 or later.
  6. 6. For BIG-IP version 13.1.x: This version has reached End of Technical Support (EoTS) and no patch is available; migrate to a supported version (14.1.5.6+, 15.1.10.2+, or 16.1.4.1+).
  7. 7. After upgrade, verify the fix by confirming the system is running the patched version using 'tmsh show sys version'.
  8. 8. Review BIG-IP Configuration Utility access logs for any suspicious activity consistent with the vulnerability exploitation.
Caveat Major version upgrades (e.g., 13.1.x to 16.1.x) may require significant testing and configuration review; always review F5 release notes for compatibility concerns and ensure custom configurations are compatible with the target version.

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
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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