dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6669

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.2, 14.0.0-14.0.1, 13.1.0-13.1.3.1, 12.1.0-12.1.5, and 11.5.1-11.6.5.1, undisclosed traffic flow may cause TMM to restart under some circumstances.

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

This is a denial of service vulnerability in F5 BIG-IP where undisclosed traffic flow patterns can cause the Traffic Management Microkernel (TMM) to restart under certain conditions, potentially disrupting traffic processing.

MitigationApply F5's security updates to upgrade BIG-IP to a fixed version outside the affected version ranges.

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.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip AnalyticsApplication
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Domain Name SystemApplication
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.1, <= 11.6.5.1>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3.1>= 14.0.0, <= 14.0.1>= 14.1.0, <= 14.1.2>= 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. Confirm F5 BIG-IP product installation
    Run 'tmsh show sys hardware' or check the system banner at login to confirm the device is F5 BIG-IP
    Affected if The system is not a F5 BIG-IP device
  2. Identify installed BIG-IP version
    Run 'tmsh show sys version' or check System > Overview in the web UI to find the installed TMOS version
    Affected if Unable to determine the installed version
  3. Compare version against affected ranges
    Match the installed version number to the following affected ranges: 11.5.1-11.6.5.1, 12.1.0-12.1.5, 13.1.0-13.1.3.1, 14.0.0-14.0.1, 14.1.0-14.1.2, 15.0.0-15.0.1
    Affected if The installed version falls within any of these ranges
  4. Check TMM restart events
    Review logs with 'tmsh show /ltm node' and check /var/log/ltm for TMM restart messages or core dumps
    Affected if Unexpected TMM restarts are occurring without known cause
  5. Verify module presence
    Run 'tmsh list sys module' to list enabled BIG-IP modules - the vulnerability applies to APM, AFM, Analytics, AAM, ASM, DNS, Edge Gateway, and FPS modules
    Affected if Any of these modules are enabled on a vulnerable version

The environment is affected if the installed BIG-IP version falls within any of the affected version ranges (11.5.1-11.6.5.1, 12.1.0-12.1.5, 13.1.0-13.1.3.1, 14.0.0-14.0.1, 14.1.0-14.1.2, or 15.0.0-15.0.1) and one of the vulnerable modules is enabled.

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 F5's security updates to upgrade BIG-IP to a fixed version outside the affected version ranges.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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