CVE-2020-5925
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 BIG-IP versions 15.1.0-15.1.0.4, 15.0.0-15.0.1.3, 14.1.0-14.1.2.6, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, and 11.6.1-11.6.5.1, undisclosed internally generated UDP traffic may cause the Traffic Management Microkernel (TMM) to restart under some circumstances.
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 confidenceA denial of service vulnerability in F5 BIG-IP allows specially crafted undisclosed internally generated UDP traffic to trigger a Traffic Management Microkernel (TMM) restart. Since TMM handles all packet processing, this causes complete traffic interruption until TMM recovers.
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>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.7>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 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.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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed BIG-IP versionRun command: tmsh show sys version or log into the web UI and navigate to Overview > Summary to view the system versionAffected if The version falls within any of these ranges: 11.6.1 to 11.6.5.1, 12.1.0 to 12.1.5.1, 13.1.0 to 13.1.3.3, 14.1.0 to 14.1.2.6, 15.0.0 to 15.0.1.3, or 15.1.0 to 15.1.0.4
-
Determine which BIG-IP modules are licensed and runningRun command: tmsh list sys module and check the Status column, or view System > Resource Provisioning in the web UIAffected if Any of these modules are provisioned: Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, Domain Name System, Fraud Protection Service, or Global Traffic Manager
-
Verify UDP traffic processing is enabledCheck for any UDP virtual servers, UDP profiles, or UDP-based services configured. Run: tmsh list ltm virtual where type is udp, or review network configuration for UDP listenersAffected if The system is configured to process UDP traffic (any UDP virtual server, profile, or DNS/UDP service is active)
If the BIG-IP version is within the affected ranges AND any of the listed modules are provisioned AND UDP traffic is being processed, the system is vulnerable to TMM restarts causing denial of service.
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 data11.6.5.212.1.5.213.1.3.4
Upgrade BIG-IP to a patched version beyond 15.1.0.4/15.0.1.3/14.1.2.6/13.1.3.3/12.1.5.1/11.6.5.1. Schedule during maintenance window as upgrade will cause TMM restart and service interruption.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5925 — 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-5925 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