Big Ip Access Policy ManagerApplication · F5
CVE-2019-6678
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 · uneditedOn BIG-IP versions 15.0.0-15.0.1, 14.1.0-14.1.2.2, 14.0.0-14.0.1, and 13.1.0-13.1.3.1, the TMM process may restart when the packet filter feature is enabled.
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 confidenceOn F5 BIG-IP versions 15.0.0-15.0.1, 14.1.0-14.1.2.2, 14.0.0-14.0.1, and 13.1.0-13.1.3.1, the TMM (Traffic Management Microkernel) process may restart when the packet filter feature is enabled, causing a denial of service condition.
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
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip Advanced Firewall ManagerApplication
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip AnalyticsApplication
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip Application Acceleration ManagerApplication
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip Application Security ManagerApplication
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip Domain Name SystemApplication
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip Edge GatewayWeb browser
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.1
Big Ip Fraud Protection ServiceApplication
>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.0.1.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 the installed BIG-IP versionRun `tmsh show /sys version` or check the BIG-IP GUI under Dashboard > System > Software VersionAffected if The version falls within 13.1.0-13.1.3.1, 14.0.0-14.0.1, 14.1.0-14.1.2.2, or 15.0.0-15.0.1
-
Confirm the affected module is in useCheck which BIG-IP modules (APM, AFM, Analytics, AAM, ASM, DNS, Edge Gateway, or Fraud Protection Service) are licensed and active on the system using `tmsh show /sys license`Affected if Any of the listed modules are provisioned and active on a vulnerable version
You are affected if your BIG-IP version is within the vulnerable ranges AND the packet filter feature is enabled, causing TMM to be at risk of restart and 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 data13.1.3.214.0.1.114.1.2.3
If packet filter is not required, disable the packet filter feature. Otherwise, upgrade to a patched BIG-IP version that resolves this issue.
Fix this in Big Ip Access Policy Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6678 — 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-2019-6678 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