dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6673

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 versions 15.0.0-15.0.1 and 14.0.0-14.1.2, when the BIG-IP is configured in HTTP/2 Full Proxy mode, specifically crafted requests may cause a disruption of service provided by the Traffic Management Microkernel (TMM).

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

In BIG-IP versions 15.0.0-15.0.1 and 14.0.0-14.1.2, when configured in HTTP/2 Full Proxy mode, specially crafted HTTP/2 requests can cause the Traffic Management Microkernel (TMM) to fail, resulting in denial of service.

MitigationUpgrade BIG-IP to version 15.0.2 or later (for 15.x) and 14.1.3 or later (for 14.x), or disable HTTP/2 Full Proxy mode if immediate upgrade is not feasible.

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:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Application Security ManagerApplication
Affected:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Link ControllerApplication
Affected:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Local Traffic ManagerApplication
Affected:>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Policy Enforcement ManagerApplication
Affected:>= 14.0.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. Identify the BIG-IP version
    Run 'tmsh show sys version' or check the BIG-IP GUI under Dashboard > System > Software Version
    Affected if The version is 14.0.0-14.1.2 or 15.0.0-15.0.1
  2. Confirm HTTP/2 Full Proxy mode is enabled
    Run 'tmsh list ltm profile http2' to list all HTTP/2 profiles, then inspect each profile with 'tmsh list ltm profile http2 <profile_name>' and check for 'parent default-http2' which indicates full proxy mode is in use
    Affected if An HTTP/2 profile exists and is associated with a virtual server using HTTP/2 Full Proxy mode (the default mode)
  3. Verify the HTTP/2 profile is applied to a virtual server
    Run 'tmsh list ltm virtual <virtual_name>' and look for the 'profile' section containing 'http2'
    Affected if A virtual server references an HTTP/2 profile, meaning traffic using that profile could trigger the vulnerability

The environment is affected only if the BIG-IP version falls within 14.0.0-14.1.2 or 15.0.0-15.0.1 AND HTTP/2 Full Proxy mode is actively configured and in use by at least one virtual server.

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

Upgrade BIG-IP to version 15.0.2 or later (for 15.x) and 14.1.3 or later (for 14.x), or disable HTTP/2 Full Proxy mode if immediate upgrade is not feasible.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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