dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2020-27723

HIGH · 7.5 CVSS v3.1 Published 2020-12-24
Fix available
A fix is available. Upgrade to 13.1.3.5 / 14.1.3.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
In versions 14.1.0-14.1.3 and 13.1.0-13.1.3.4, a BIG-IP APM virtual server processing PingAccess requests may lead to a restart of the Traffic Management Microkernel (TMM) process.

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 vulnerability in F5 BIG-IP APM versions 14.1.0-14.1.3 and 13.1.0-13.1.3.4 allows a specially crafted PingAccess request to trigger a restart of the Traffic Management Microkernel (TMM), causing a denial of service condition.

MitigationUpgrade BIG-IP to a version beyond 14.1.3 (for 14.x) or 13.1.3.4 (for 13.x) to remediate this vulnerability.

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:>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.0

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. Confirm BIG-IP APM module is installed
    Run 'tmsh list apm' or check via web UI under Access Policy > Access Profiles
    Affected if APM module is present and running
  2. Check BIG-IP version
    Run 'tmsh show sys version' or check via web UI under System > Software > Image
    Affected if Version is 13.1.0-13.1.3.4, 14.1.0-14.1.3.0, or 15.0.0-15.1.0
  3. Verify PingAccess integration is configured
    Check APM access profiles for PingAccess agent settings under Access Policy > PingAccess > Agent Configuration
    Affected if PingAccess agent is configured and enabled in APM

User is affected if BIG-IP APM is running with a version in the ranges 13.1.0-13.1.3.4, 14.1.0-14.1.3.0, or 15.0.0-15.1.0 and PingAccess integration is configured.

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 13.1.3.5 / 14.1.3.1 / 15.1.0 or later
Fixed in 13.1.3.514.1.3.115.1.0
Interim mitigation

Upgrade BIG-IP to a version beyond 14.1.3 (for 14.x) or 13.1.3.4 (for 13.x) to remediate this vulnerability.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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