Big Ip Application Security ManagerApplication · F5
CVE-2020-5927
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 · uneditedIn versions 15.1.0-15.1.0.4, 15.0.0-15.0.1.3, and 14.1.0-14.1.2.6, BIG-IP ASM Configuration utility Stored-Cross Site Scripting.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in the BIG-IP ASM (Application Security Manager) Configuration utility. Malicious scripts can be injected and permanently stored, executing in the browsers of users who access the affected configuration pages.
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 Application Security ManagerApplication
>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm BIG-IP ASM module is provisionedRun `tmsh show sys provision` or check the web UI under System > Platform > Provisioning to verify ASM is provisioned/enabledAffected if ASM is not provisioned or not installed - the vulnerability only affects the ASM Configuration utility
-
Identify the installed BIG-IP versionRun `tmsh show sys version` or check the version displayed in the web UI login page footerAffected if Cannot determine version - version must be known to assess vulnerability
-
Compare version against affected rangesCheck if the installed version falls within: 14.1.0 - 14.1.2.6, 15.0.0 - 15.0.1.3, or 15.1.0 - 15.1.0.4Affected if Version matches one of the vulnerable ranges (any version >= 14.1.0 < 14.1.2.7, >= 15.0.0 < 15.0.1.4, or >= 15.1.0 < 15.1.0.5)
-
Verify ASM Configuration utility is accessibleAttempt to access the ASM Configuration utility at /tmui/ (the vulnerable endpoint) via the web interfaceAffected if The Configuration utility is accessible and ASM is enabled - this confirms attack surface exists
You are affected if BIG-IP ASM is provisioned and the installed version falls within any of the three vulnerable version ranges.
Generated from the published advisory. Verify against your own configuration.
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 data14.1.2.715.0.1.415.1.0.5
Apply the appropriate F5 hotfix/patch for the respective version branch (15.1.x, 15.0.x, or 14.1.x). Review ASM policy configurations and sanitize any user-supplied input in the Configuration utility.
Fix this in Big Ip Application Security Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5927 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5927 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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