dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6604

MEDIUM · 6.8 CVSS v3.0 Published 2019-03-28
Fix available
A fix is available. Upgrade to after 13.1.1 or later.
See remediation →
77/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 11.5.1-11.5.8, 11.6.1-11.6.3, 12.1.0-12.1.3.6, 13.0.0-13.1.1.1, and 14.0.0-14.0.0.2, under certain conditions, hardware systems with a High-Speed Bridge and using non-default Layer 2 forwarding configurations may experience a lockup of the High-Speed Bridge.

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 hardware where the High-Speed Bridge can lock up when using non-default Layer 2 forwarding configurations on affected versions (11.5.1-14.0.0.2). The lockup occurs under specific, unspecified conditions and renders the bridge non-functional.

MitigationUpdate affected BIG-IP systems to a patched version beyond 14.0.0.2. Prior to patching, identify systems using High-Speed Bridge with non-default L2 forwarding and implement compensating network controls to maintain availability.

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.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Edge GatewayWeb browser
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Global Traffic ManagerApplication
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Link ControllerApplication
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0
Big Ip Local Traffic ManagerApplication
Affected:>= 11.2.1, <= 11.5.8>= 11.6.0, <= 11.6.3>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1= 14.0.0

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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 installed BIG-IP version
    Run command: tmsh show sys version or log into the BIG-IP Configuration Utility and check System > Overview > Software Version
    Affected if Version is 11.5.1 through 14.0.0 (inclusive) or falls within ranges 11.5.1-11.5.8, 11.6.0-11.6.3, 12.1.0-12.1.3, 13.0.0-13.1.1, or exactly 14.0.0
  2. Verify High-Speed Bridge is configured
    Run command: tmsh list /net bridge or check via Configuration Utility under Network > Bridges
    Affected if Any High-Speed Bridge objects exist in the configuration
  3. Confirm Layer 2 forwarding configuration
    Run command: tmsh list /net bridge all-properties and examine the forwarding-mode setting, or inspect the bridge configuration for any L2-specific forwarding parameters
    Affected if Non-default L2 forwarding settings are present (anything other than default layer 3 forwarding)
  4. Check for module availability
    Run command: tmsh list /sys module or check which BIG-IP modules (APM, AFM, AAM, etc.) are licensed and loaded
    Affected if Any of the affected modules (APM, AFM, AAM, Edge Gateway, FPS, GTM, LC, LTM) are installed on an affected version

Environment is affected if running a vulnerable BIG-IP version (11.5.1-14.0.0) with High-Speed Bridge configured using non-default L2 forwarding.

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 13.1.1
Interim mitigation

Update affected BIG-IP systems to a patched version beyond 14.0.0.2. Prior to patching, identify systems using High-Speed Bridge with non-default L2 forwarding and implement compensating network controls to maintain availability.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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