dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2019-6471

MEDIUM · 5.9 CVSS v3.1 Published 2019-10-09
Fix available
A fix is available. Upgrade to after 13.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A race condition which may occur when discarding malformed packets can result in BIND exiting due to a REQUIRE assertion failure in dispatch.c. Versions affected: BIND 9.11.0 -> 9.11.7, 9.12.0 -> 9.12.4-P1, 9.14.0 -> 9.14.2. Also all releases of the BIND 9.13 development branch and version 9.15.0 of the BIND 9.15 development branch and BIND Supported Preview Edition versions 9.11.3-S1 -> 9.11.7-S1.

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 race condition in BIND's packet handling code causes the DNS server to crash when processing malformed packets. The vulnerability triggers a REQUIRE assertion failure in dispatch.c, resulting in denial of service.

MitigationUpgrade BIND to versions 9.11.8+, 9.12.5+, 9.14.3+, or later stable releases that contain the fix for this assertion failure.

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 Local Traffic ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip AnalyticsApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip Access Policy ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip Application Security ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.0.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.1.0, <= 13.1.1= 14.0.0= 14.1.0= 15.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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 F5 Big-IP product module
    Log into the F5 BIG-IP GUI or use the command line 'tmsh show sys module' to list installed modules
    Affected if The system is running any of these modules: Local Traffic Manager, Application Acceleration Manager, Advanced Firewall Manager, Analytics, Access Policy Manager, Application Security Manager, Edge Gateway, or Fraud Protection Service
  2. Check the installed product version
    Run 'tmsh show sys version' or check the BIG-IP GUI under Dashboard > System > Platform Information to obtain the exact version number
    Affected if The version falls within these ranges: 11.5.2-11.5.9, 11.6.1-11.6.4, 12.1.0-12.1.4, 13.1.0-13.1.1, or equals 14.0.0, 14.1.0, or 15.0.0
  3. Verify DNS services are configured
    Check if DNS profiles or DNS services are enabled on the BIG-IP device using 'tmsh list ltm dns' or by reviewing the DNS configuration in the GUI under Local Traffic > Profiles > Services > DNS
    Affected if DNS profiles or DNS services are actively configured on the device
  4. Confirm BIND version if accessible
    If the underlying BIND version is exposed, check it with 'named -v' or review the BIG-IP release notes for the bundled BIND version
    Affected if The bundled BIND version matches the vulnerable versions known to contain the REQUIRE assertion flaw in dispatch.c

The environment is affected if it runs any of the listed F5 Big-IP modules and the version matches one of the specific vulnerable version ranges, with DNS services 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 13.1.1
Interim mitigation

Upgrade BIND to versions 9.11.8+, 9.12.5+, 9.14.3+, or later stable releases that contain the fix for this assertion failure.

Fix this in Big Ip Local Traffic Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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