Big Ip Access Policy ManagerApplication · F5

CVE-2021-23041

MEDIUM · 6.1 CVSS v3.1 Published 2021-09-14
Fix available
A fix is available. Upgrade to 13.1.4.1 / 14.1.4.2 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 BIG-IP version 16.0.x before 16.0.1.2, 15.1.x before 15.1.3, 14.1.x before 14.1.4.2, 13.1.x before 13.1.4.1, and all versions of 12.1.x, a DOM based cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP Configuration utility that allows an attacker to execute JavaScript in the context of the current 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

DOM-based cross-site scripting (XSS) vulnerability in undisclosed page of BIG-IP Configuration utility allows attackers to execute JavaScript in the context of the current logged-in user. The vulnerability affects multiple version branches including 12.1.x (all versions), 13.1.x before 13.1.4.1, 14.1.x before 14.1.4.2, 15.1.x before 15.1.3, and 16.0.x before 16.0.1.2.

MitigationUpgrade to BIG-IP version 16.0.1.2 or later, 15.1.3 or later, 14.1.4.2 or later, or 13.1.4.1 or later. For 12.1.x (all versions) which has no fix, consider disabling the Configuration utility if not required or implementing additional input validation controls.

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:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip Advanced Web Application FirewallApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip AnalyticsApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip Application Security ManagerApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip Domain Name SystemApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.1.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.4.1>= 14.1.0, < 14.1.4.2>= 15.1.0, < 15.1.3>= 16.0.0, < 16.0.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
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 version via tmsh
    Run the command 'tmsh show /sys version' or 'tmsh show /sys version detail' to retrieve the installed version number
    Affected if The displayed version falls within any of these ranges: 12.1.0-12.1.6, 13.1.0-13.1.4.0, 14.1.0-14.1.4.1, 15.1.0-15.1.2, or 16.0.0-16.0.1.1
  2. Verify Configuration utility is accessible
    Confirm the BIG-IP Configuration utility (web-based management interface) is enabled and reachable on the management IP or via a virtual server
    Affected if The Configuration utility is accessible over the network without additional authentication beyond the login page
  3. Confirm affected module is licensed
    Check which BIG-IP modules are licensed and running on the system using 'tmsh show /sys license' or by reviewing the modules listed in the web interface
    Affected if Any of these modules are licensed: Access Policy Manager, Advanced Firewall Manager, Advanced Web Application Firewall, Analytics, Application Acceleration Manager, Application Security Manager, Domain Name System, or Fraud Protection Service
  4. Cross-reference version with affected branches
    Compare your installed version against the known vulnerable branches: 12.1.x (all versions), 13.1.x before 13.1.4.1, 14.1.x before 14.1.4.2, 15.1.x before 15.1.3, or 16.0.x before 16.0.1.2
    Affected if Your version matches any of the vulnerable version ranges listed above

You are affected if the BIG-IP Configuration utility is accessible and the installed version falls within 12.1.0-12.1.6, 13.1.0-13.1.4.0, 14.1.0-14.1.4.1, 15.1.0-15.1.2, or 16.0.0-16.0.1.1.

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 13.1.4.1 / 14.1.4.2 / 15.1.3 or later
Fixed in 13.1.4.114.1.4.215.1.3
Interim mitigation

Upgrade to BIG-IP version 16.0.1.2 or later, 15.1.3 or later, 14.1.4.2 or later, or 13.1.4.1 or later. For 12.1.x (all versions) which has no fix, consider disabling the Configuration utility if not required or implementing additional input validation controls.

Recommended fix High confidence

Upgrade to the latest available version in your branch: 13.1.4.1+, 14.1.4.2+, 15.1.3+, or ideally 16.0.1.2+

  1. 1. Identify the current BIG-IP version by checking System > Software Management > ISO Image or using 'tmsh show sys version' command
  2. 2. Determine which version branch you are on (12.1.x, 13.1.x, 14.1.x, or 15.1.x)
  3. 3. For version 12.1.x: This version has reached End of Technical Support (EoTS) and has no patch; plan migration to a supported version branch (13.1.4.1+, 14.1.4.2+, or 15.1.3+)
  4. 4. For version 13.1.x: Upgrade to 13.1.4.1 or later
  5. 5. For version 14.1.x: Upgrade to 14.1.4.2 or later
  6. 6. For version 15.1.x: Upgrade to 15.1.3 or later
  7. 7. Download the appropriate ISO image from the F5 Networks downloads portal (support.f5.com)
  8. 8. Upload the new software version via BIG-IP Configuration utility (System > Software Management > ISO Image) or via tmsh
Caveat Version 12.1.x is End of Technical Support with no patch available - requires migration to a supported version branch; ensure compatibility testing with existing configurations before upgrading

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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