dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-38423

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-02
Fix available
A fix is available. Upgrade to 14.1.5.5 / 15.1.9.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP Configuration utility that allows an attacker to run JavaScript in the context of the currently logged-in user.  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 stored cross-site scripting (XSS) vulnerability exists in the BIG-IP Configuration utility, allowing an attacker to inject malicious JavaScript that executes in the context of the currently logged-in user. The vulnerability is located in an undisclosed page of the web-based management interface. An attacker would need to persuade a user to visit the affected page to trigger the injected script.

MitigationApply the vendor-supplied patch for BIG-IP versions still under support, as indicated by F5's security advisory. Until patched, restrict access to the Configuration utility to trusted users only and monitor for suspicious activity.

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.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip Advanced Web Application FirewallApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip Application Visibility And ReportingApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.0.2
Big Ip Carrier Grade NatApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.5>= 15.1.0, < 15.1.9.1>= 16.1.0, < 16.1.3.5>= 17.0.0, < 17.1.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed BIG-IP version
    Run the command `tmsh show /sys version` or check the file `/etc/product_version` on the BIG-IP device
    Affected if The displayed version falls within any of these ranges: 13.1.0-13.1.5, 14.1.0-14.1.5.4, 15.1.0-15.1.9.0, 16.1.0-16.1.3.4, or 17.0.0-17.1.0.1
  2. Verify the Configuration utility is accessible
    Confirm that the BIG-IP web-based management interface (Configuration utility) is enabled and reachable on port 443 or the configured admin port
    Affected if The Configuration utility is accessible over the network to any user
  3. Confirm BIG-IP modules are licensed and running
    Run `tmsh list sys module` to list all licensed BIG-IP modules
    Affected if Any of these modules are licensed and running: APM, AFM, ASM, AVR, AAM, or Analytics, since the vulnerability affects all listed modules in the affected version ranges

You are affected if your BIG-IP version falls within the affected ranges and the Configuration utility is accessible to users who could be persuaded to visit the vulnerable page.

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.5 / 15.1.9.1 / 16.1.3.5 or later
Fixed in 14.1.5.515.1.9.116.1.3.5
Interim mitigation

Apply the vendor-supplied patch for BIG-IP versions still under support, as indicated by F5's security advisory. Until patched, restrict access to the Configuration utility to trusted users only and monitor for suspicious activity.

Recommended fix High confidence

Upgrade to 14.1.5.5+ (for 14.1.x), 15.1.9.1+ (for 15.1.x), or 16.1.3.5+ (for 16.1.x) depending on your current branch

  1. 1. Identify the currently installed BIG-IP version by checking System > Software Management > ISO Image or running 'tmsh show sys version'
  2. 2. Determine which version branch your current installation belongs to (13.1.x, 14.1.x, 15.1.x, or 16.1.x)
  3. 3. For 13.1.x branch: Plan migration to a later branch (14.1.x or higher) as 13.1.x is at or below end of technical support
  4. 4. For 14.1.x: Upgrade to version 14.1.5.5 or later
  5. 5. For 15.1.x: Upgrade to version 15.1.9.1 or later
  6. 6. For 16.1.x: Upgrade to version 16.1.3.5 or later
  7. 7. Download the appropriate ISO image from downloads.f5.com
  8. 8. Upload and install the new version via BIG-IP Configuration utility (System > Software Management > ISO Image > Upload)
Caveat Minor: Review release notes for any configuration changes between versions; ensure compatibility with dependent applications before production deployment

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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