dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-28707

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
On F5 BIG-IP 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5.1, and 14.1.x versions prior to 14.1.4.6, a stored cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP Configuration utility (also referred to as the BIG-IP TMUI) that allows an attacker to execute 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 · high confidence

Stored cross-site scripting (XSS) vulnerability in an undisclosed page of the F5 BIG-IP Configuration utility (TMUI) allows attackers to inject malicious JavaScript that executes in the context of the currently logged-in user. This is a persistent XSS vulnerability affecting BIG-IP versions 16.1.x before 16.1.2.2, 15.1.x before 15.1.5.1, and 14.1.x before 14.1.4.6.

MitigationUpgrade BIG-IP to version 16.1.2.2, 15.1.5.1, or 14.1.4.6 or later. If immediate patching is not feasible, restrict access to the Configuration utility to trusted administrative networks only, or disable TMUI access if not 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:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip AnalyticsApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Application Acceleration ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Application Security ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Domain Name SystemApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Fraud Protection ServiceApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1
Big Ip Global Traffic ManagerApplication
Affected:= 14.1.0= 14.1.2= 14.1.3= 14.1.4= 15.1.0= 15.1.1= 15.1.2= 15.1.3= 15.1.4= 15.1.5= 16.1.0= 16.1.1

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. Check BIG-IP version via command line
    Run `tmsh show /sys version` or `bigpipe version` on the command line to retrieve the installed version
    Affected if The version shown is 14.1.x before 14.1.4.6, 15.1.x before 15.1.5.1, or 16.1.x before 16.1.2.2, or matches any of these specific versions: 14.1.0, 14.1.2, 14.1.3, 14.1.4, 15.1.0, 15.1.1, 15.1.2, 15.1.3, 15.1.4, 15.1.5, 16.1.0, 16.1.1
  2. Check BIG-IP version via TMUI
    Log into the Configuration utility (TMUI) and navigate to System > Software Management > ISO Image, or check the version displayed on the TMUI login page footer
    Affected if The displayed version matches the affected versions listed above
  3. Verify TMUI accessibility
    Determine if the Configuration utility (port 443 or 8443) is exposed to untrusted networks by reviewing network access lists or firewall rules
    Affected if TMUI is accessible from networks outside the trusted administrative zone
  4. Identify affected modules
    Confirm which F5 modules are licensed and running: APM, AFM, Analytics, AAM, ASM, DNS, FPS, or GTM. Check via `tmsh show /sys module` or TMUI main page
    Affected if Any of these modules (Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, Domain Name System, Fraud Protection Service, Global Traffic Manager) are licensed and the version is vulnerable

A system is affected if it runs BIG-IP version 14.1.x before 14.1.4.6, 15.1.x before 15.1.5.1, or 16.1.x before 16.1.2.2, and has the Configuration utility (TMUI) accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade BIG-IP to version 16.1.2.2, 15.1.5.1, or 14.1.4.6 or later. If immediate patching is not feasible, restrict access to the Configuration utility to trusted administrative networks only, or disable TMUI access if not required.

Recommended fix High confidence

BIG-IP 14.1.4.6 or later (or upgrade to 15.1.5.1+/16.1.2.2+ for additional fixes)

  1. 1. Identify the current BIG-IP TMUI (Configuration utility) version by navigating to System > Software Management > ISO Image or checking the version via tmsh: show sys version
  2. 2. Download the fixed BIG-IP version 14.1.4.6 or later from the F5 Downloads portal at https://downloads.f5.com/
  3. 3. Upload the ISO image to the BIG-IP device via the web interface (System > Software Management > ISO Image) or via tmsh: install sys software iso <filename>
  4. 4. Create a new boot partition (Volume) for the new image using the software management interface or tmsh: create sys software volume <volume-name> image <filename>
  5. 5. Install the new software version to the new volume: install sys software <software-name> volume <volume-name> no-boot
  6. 6. Reboot the BIG-IP device to boot from the new volume: reboot <volume-name>
  7. 7. After the system restarts, verify the new version is running: show sys version
  8. 8. Confirm the vulnerability is resolved by accessing the Configuration utility and validating the undisclosed page no longer executes unsanitized JavaScript
Caveat Upgrading BIG-IP TMUI may require downtime; test in staging environment first; some configuration compatibility should be verified between major version jumps

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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