Big Ip Access Policy ManagerApplication · F5
CVE-2020-27724
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 APM versions 16.0.0-16.0.0.1, 15.1.0-15.1.0.4, 15.0.0-15.0.1.3, 14.1.0-14.1.3, 13.1.0-13.1.3.4, 12.1.0-12.1.5.2, and 11.6.1-11.6.5.2, on systems running more than one TMM instance, authenticated VPN users may consume excessive resources by sending specially-crafted malicious traffic over the tunnel.
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 confidenceAuthenticated VPN users can send specially-crafted malicious traffic over the tunnel to consume excessive resources on BIG-IP APM systems running multiple TMM instances, potentially causing denial of service.
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
>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.0.1.4>= 15.1.0, < 15.1.0.5>= 16.0.0, < 16.0.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 BIG-IP system versionRun 'tmsh show sys version' or check the web UI under Diagnostics > Upgrade > ISO Image to view the installed BIG-IP versionAffected if The installed version falls within any of these ranges: 11.6.1-11.6.5, 12.1.0-12.1.5, 13.1.0-13.1.3.4, 14.1.0-14.1.3.0, 15.0.0-15.0.1.3, 15.1.0-15.1.0.4, or 16.0.0-16.0.0
-
Verify APM module is provisionedRun 'tmsh show sys provision' or check under System > Resource Provisioning in the web UI to confirm APM module is provisionedAffected if APM shows as provisioned (Nominal or Dedicated) - if APM is not provisioned, the system is not affected
-
Confirm multiple TMM instances existRun 'tmsh show sys tmm-info' to list TMM instances, or check the system hardware inventory for multiple TMM chipsAffected if The system shows more than one TMM instance (typical on chassis-based or clustered systems) - single TMM systems are not affected
-
Check for active VPN or Access Policy configurationsRun 'tmsh list apm profile access' to list access profiles, or check under Access Policy > Access Profiles in the web UIAffected if Any access profiles with VPN capabilities exist - the vulnerability requires VPN traffic over the tunnel to be exploited
A system is affected if it runs an affected BIG-IP version, has APM provisioned, operates with multiple TMM instances, and has VPN/access profiles configured for authenticated users.
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 data13.1.3.514.1.3.115.0.1.4
Apply the vendor-supplied patches for the affected BIG-IP APM versions to resolve the resource exhaustion vulnerability.
Fix this in Big Ip Access Policy Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27724 — 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-27724 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