dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6624

HIGH · 7.5 CVSS v3.0 Published 2019-07-02
Fix available
A fix is available. Upgrade to after 14.1.0.5 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 14.1.0-14.1.0.5, 14.0.0-14.0.0.4, 13.0.0-13.1.1.4, and 12.1.0-12.1.4, an undisclosed traffic pattern sent to a BIG-IP UDP virtual server may lead to a denial-of-service (DoS).

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 confidence

A denial-of-service vulnerability exists in F5 BIG-IP devices running the affected versions. An attacker can send a specific, undisclosed traffic pattern to a UDP virtual server, causing the device to become unresponsive or crash, disrupting service for all traffic handled by that virtual server.

MitigationUpgrade BIG-IP to version 14.1.0.6 or later (for 14.1.x), 14.0.0.5 or later (for 14.0.x), 13.1.1.5 or later (for 13.x), or 12.1.4.1 or later (for 12.x). If immediate patching is not feasible, consider implementing rate limiting or traffic filtering on the UDP virtual server as a temporary measure.

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:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip Link ControllerApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip Policy Enforcement ManagerApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip WebacceleratorApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip Application Security ManagerApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5
Big Ip Local Traffic ManagerApplication
Affected:>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.0.0.4>= 14.1.0, <= 14.1.0.5

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.0/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. Determine BIG-IP version
    Run 'tmsh show sys version' or check the BIG-IP UI under Dashboard > System Information > Version
    Affected if The installed version falls within 12.1.0-12.1.4, 13.0.0-13.1.1.4, 14.0.0-14.0.0.4, or 14.1.0-14.1.0.5
  2. Identify provisioned modules
    Run 'tmsh list sys provision' to see which BIG-IP modules are licensed and provisioned
    Affected if Any of these modules are provisioned: Access Policy Manager, Advanced Firewall Manager, Application Acceleration Manager, Link Controller, Policy Enforcement Manager, WebAccelerator, Application Security Manager, or Local Traffic Manager
  3. Check for UDP virtual servers
    Run 'tmsh list ltm virtual' and look for 'protocol udp' in the output, or check the virtual server configuration in the GUI under Local Traffic > Virtual Servers
    Affected if Any virtual server is configured with UDP as the protocol (the attack requires a UDP virtual server to receive the malicious traffic pattern)

If the BIG-IP version is within the affected ranges AND a UDP virtual server is configured, the environment is vulnerable to CVE-2019-6624.

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

Upgrade BIG-IP to version 14.1.0.6 or later (for 14.1.x), 14.0.0.5 or later (for 14.0.x), 13.1.1.5 or later (for 13.x), or 12.1.4.1 or later (for 12.x). If immediate patching is not feasible, consider implementing rate limiting or traffic filtering on the UDP virtual server as a temporary measure.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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