dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2020-5904

HIGH · 8.8 CVSS v3.1 Published 2020-07-01
Fix available
A fix is available. Upgrade to after 15.1.0.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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.0.0-15.1.0.3, 14.1.0-14.1.2.5, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, a cross-site request forgery (CSRF) vulnerability in the Traffic Management User Interface (TMUI), also referred to as the Configuration utility, exists in an undisclosed page.

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 cross-site request forgery (CSRF) vulnerability exists in the BIG-IP Traffic Management User Interface (TMUI) configuration utility. The flaw allows an attacker to potentially trick authenticated users into performing unintended actions on the BIG-IP device. The vulnerability affects undisclosed pages in versions 15.0.0-15.1.0.3, 14.1.0-14.1.2.5, 13.1.0-13.1.3.3, and 12.1.0-12.1.5.1.

MitigationApply the appropriate F5 security patch or upgrade BIG-IP to a supported, patched version as specified in the F5 advisory.

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.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip AnalyticsApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Application Security ManagerApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Domain Name SystemApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Fraud Protection ServiceApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.1.0.3
Big Ip Global Traffic ManagerApplication
Affected:>= 12.1.0, <= 12.1.5.1>= 13.1.0, <= 13.1.3.3>= 14.1.0, <= 14.1.2.5>= 15.0.0, <= 15.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 the BIG-IP version
    Run `tmsh show sys version` or check `/etc/product_version` to retrieve the installed BIG-IP version number
    Affected if The installed version falls within 12.1.0-12.1.5.1, 13.1.0-13.1.3.3, 14.1.0-14.1.2.5, or 15.0.0-15.1.0.3
  2. Confirm installed modules
    Run `tmsh list sys provision` to list all provisioned BIG-IP modules (APM, AFM, ASM, DNS, GTM, etc.)
    Affected if Any of the affected modules (APM, AFM, Analytics, AAM, ASM, DNS, FPS, GTM) are provisioned on the device
  3. Verify TMUI accessibility
    Check if the Traffic Management User Interface is accessible by attempting to reach the TMUI login page on port 443 or 8443, or by reviewing the httpd configuration with `tmsh list sys httpd`
    Affected if TMUI is accessible and the version falls within the affected ranges
  4. Check TMUI exposure
    Review the BIG-IP network configuration to determine if TMUI is exposed to untrusted networks, or inspect the management interface settings
    Affected if TMUI is exposed to external or untrusted networks while running an affected version

A defender is affected if their BIG-IP version is within 12.1.0-12.1.5.1, 13.1.0-13.1.3.3, 14.1.0-14.1.2.5, or 15.0.0-15.1.0.3 and any affected module is provisioned with 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.

From vendor data
Upgrade available Upgrade to a release after 15.1.0.3
Interim mitigation

Apply the appropriate F5 security patch or upgrade BIG-IP to a supported, patched version as specified in the F5 advisory.

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-5904 — 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-5904 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