dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2020-5862

HIGH · 7.5 CVSS v3.1 Published 2020-03-27
Fix available
A fix is available. Upgrade to after 15.1.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 BIG-IP 15.1.0-15.1.0.1, 15.0.0-15.0.1.1, and 14.1.0-14.1.2.2, under certain conditions, TMM may crash or stop processing new traffic with the DPDK/ENA driver on AWS systems while sending traffic. This issue does not affect any other platforms, hardware or virtual, or any other cloud provider since the affected driver is specific to AWS.

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

A denial of service vulnerability in BIG-IP 15.1.x, 15.0.x, and 14.1.x versions allows an attacker to cause the TMM (Traffic Management Module) to crash or stop processing new traffic on AWS systems using the DPDK/ENA driver, resulting in service disruption.

MitigationUpgrade BIG-IP to a version beyond 15.1.0.1, 15.0.1.1, or 14.1.2.2. This issue is specific to AWS environments using DPDK/ENA driver and does not affect other platforms or cloud providers.

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.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip AnalyticsApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.1
Big Ip Global Traffic ManagerApplication
Affected:>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1.1>= 15.1.0, <= 15.1.0.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP version
    Run `tmsh show sys version` or view version in the web UI under System > Software Management > BIG-IP Version
    Affected if The version is 14.1.0 through 14.1.2.2, 15.0.0 through 15.0.1.1, or 15.1.0 through 15.1.0.1
  2. Confirm deployment platform is AWS
    Verify the BIG-IP instance is running on Amazon Web Services. Check via the AWS console, or run `tmsh show sys hardware` to identify the platform
    Affected if The system is running on AWS (this vulnerability does not affect other cloud providers or on-premises deployments)
  3. Verify DPDK/ENA driver is in use
    Check if the network interface uses the DPDK/ENA driver. Run `tmsh show net driver` or examine the network adapter configuration for the ENA driver on AWS network interfaces
    Affected if The ENA network driver is enabled and used for traffic processing

A system is affected only if it is running a vulnerable BIG-IP version (14.1.0-14.1.2.2, 15.0.0-15.0.1.1, or 15.1.0-15.1.0.1) AND is deployed on AWS AND uses the DPDK/ENA driver; if any of these conditions are not met, the system is not vulnerable to this CVE.

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.1
Interim mitigation

Upgrade BIG-IP to a version beyond 15.1.0.1, 15.0.1.1, or 14.1.2.2. This issue is specific to AWS environments using DPDK/ENA driver and does not affect other platforms or cloud providers.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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