dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6667

HIGH · 7.5 CVSS v3.1 Published 2019-11-27
Fix available
A fix is available. Upgrade to after 15.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.0.0-15.0.1, 14.1.0-14.1.0.5, 14.0.0-14.0.0.4, 13.1.0-13.1.1.5, 12.1.0-12.1.4.1, and 11.5.1-11.6.5, under certain conditions, TMM may consume excessive resources when processing traffic for a Virtual Server with the FIX (Financial Information eXchange) profile applied.

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 · moderate confidence

TMM (Traffic Management Module) on BIG-IP consumes excessive resources when processing traffic for Virtual Servers with the FIX (Financial Information eXchange) profile applied, under certain conditions. This leads to resource exhaustion and potential denial of service.

MitigationApply available F5 patches/upgrades to affected BIG-IP versions. If immediate patching is not feasible, evaluate disabling the FIX profile on affected Virtual Servers if not actively needed.

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:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip AnalyticsApplication
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip Domain Name SystemApplication
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.4.1>= 13.1.0, <= 13.1.1.5>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5>= 15.0.0, <= 15.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 `tmsh show sys hardware` to obtain the installed BIG-IP version. Compare this version number against the affected ranges: 11.5.1-11.6.5, 12.1.0-12.1.4.1, 13.1.0-13.1.1.5, 14.0.0-14.0.0.4, 14.1.0-14.1.0.5, and 15.0.0-15.0.1.
    Affected if The installed version falls within any of the listed affected version ranges.
  2. Identify FIX profile configuration
    Run `tmsh list ltm profile fix` to list all FIX profiles configured on the system. Then run `tmsh list ltm virtual` and inspect each virtual server for an associated FIX profile in the profile list.
    Affected if Any FIX profile exists on the system and is assigned to a virtual server.
  3. Check TMM resource utilization
    Run `tmsh show ltm global-stat tmm-stat` or `tmsh show sys tmm-stat` to examine TMM CPU and memory usage. Monitor over time for abnormally high resource consumption.
    Affected if TMM is consuming excessive CPU or memory resources, particularly when processing FIX traffic.
  4. Review virtual server FIX profile assignments
    For each virtual server identified with a FIX profile, verify the profile is actively processing traffic. Check via `tmsh show ltm virtual <virtual_name>` for traffic statistics.
    Affected if A virtual server has the FIX profile enabled and is actively processing traffic.

You are affected if your BIG-IP version is within the listed vulnerable ranges AND you have virtual servers with the FIX profile enabled and processing traffic.

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

Apply available F5 patches/upgrades to affected BIG-IP versions. If immediate patching is not feasible, evaluate disabling the FIX profile on affected Virtual Servers if not actively needed.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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