dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2020-5915

MEDIUM · 6.1 CVSS v3.1 Published 2020-08-26
Fix available
A fix is available. Upgrade to 11.6.5.2 / 12.1.5.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
In BIG-IP versions 15.1.0-15.1.0.4, 15.0.0-15.0.1.3, 14.1.0-14.1.2.3, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, and 11.6.1-11.6.5.1, an undisclosed TMUI page contains a vulnerability which allows a stored XSS when BIG-IP systems are setup in a device trust.

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 TMUI (Traffic Management User Interface) of F5 BIG-IP. When BIG-IP systems are configured with device trust, an attacker can inject malicious JavaScript into an undisclosed TMUI page that persists and executes in the browsers of other authenticated users viewing that page.

MitigationUpgrade BIG-IP to a patched version (15.1.0.5+, 14.1.2.4+, 13.1.3.4+, 12.1.5.2+, 11.6.5.2+) or implement Content Security Policy headers and limit TMUI access to trusted networks.

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:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip AnalyticsApplication
Affected:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip Application Security ManagerApplication
Affected:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip Domain Name SystemApplication
Affected:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.2, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.0.0, < 14.1.2.4>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.6.1, < 11.6.5.2>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.5>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5

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. Identify BIG-IP version
    Run 'tmsh show /sys version' on the command line or check the version displayed in the footer of the TMUI login page
    Affected if The installed version falls within any of these ranges: 11.6.1-11.6.5.1, 12.1.0-12.1.5.1, 13.1.0-13.1.3.3, 14.1.0-14.1.2.4, 15.0.0-15.0.1.3, or 15.1.0-15.1.0.4
  2. Confirm TMUI is accessible
    Verify that the Traffic Management User Interface web interface is reachable on the BIG-IP device (typically ports 443 or 8443)
    Affected if TMUI is exposed and accessible to users or networks where the attack could be launched
  3. Check if device trust is configured
    Run 'tmsh list /cm device-group' to list device groups; device trust is configured if multiple devices are shown in a trust device-group
    Affected if Device trust is configured between multiple BIG-IP devices, which is required for the XSS to propagate to other authenticated users
  4. Verify affected BIG-IP modules are installed
    Run 'tmsh list /sys module' or check the licensed modules in the TMUI under System > Resource Provisioning
    Affected if Any of these modules are provisioned: APM, AFM, Analytics, AAM, ASM, DNS, Edge Gateway, or FPS

You are affected if your BIG-IP version is in the vulnerable range AND TMUI is accessible AND device trust is configured with at least one of the affected modules installed.

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.

From vendor data
Upgrade available Upgrade to 11.6.5.2 / 12.1.5.2 / 13.1.3.4 or later
Fixed in 11.6.5.212.1.5.213.1.3.4
Interim mitigation

Upgrade BIG-IP to a patched version (15.1.0.5+, 14.1.2.4+, 13.1.3.4+, 12.1.5.2+, 11.6.5.2+) or implement Content Security Policy headers and limit TMUI access to trusted networks.

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-2020-5915 — 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-2020-5915 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