dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6663

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-15
Fix available
A fix is available. Upgrade to after 15.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
The BIG-IP 15.0.0-15.0.1, 14.0.0-14.1.2.2, 13.1.0-13.1.3.1, 12.1.0-12.1.5, and 11.5.1-11.6.5.1, BIG-IQ 7.0.0, 6.0.0-6.1.0, and 5.2.0-5.4.0, iWorkflow 2.3.0, and Enterprise Manager 3.1.1 configuration utility is vulnerable to Anti DNS Pinning (DNS Rebinding) attack.

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

This is a DNS rebinding (Anti-DNS Pinning) vulnerability in the F5 BIG-IP, BIG-IQ, iWorkflow, and Enterprise Manager configuration utilities. The vulnerability allows an attacker to bypass DNS pinning protections, potentially enabling attacks against internal network resources through the victim's browser by manipulating DNS responses to point to different IP addresses after initial resolution.

MitigationUpgrade to a patched version of BIG-IP, BIG-IQ, iWorkflow, or Enterprise Manager as specified in F5's security advisory. Consider implementing DNS validation controls and network segmentation as compensating controls if immediate patching 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:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip AnalyticsApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Domain Name SystemApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.0.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 is installed
    Run command 'tmsh show sys version' or check for F5 processes using 'ps aux | grep -i f5'
    Affected if F5 BIG-IP software is running on the system
  2. Identify the installed BIG-IP version
    Execute 'tmsh show sys version' and note the Software Version (e.g., 12.1.5, 14.1.2, 15.0.1)
    Affected if Version falls within any of these ranges: 11.5.2-11.6.5, 12.1.0-12.1.5, 13.0.0-13.1.3, 14.0.0-14.1.2, or 15.0.0-15.0.1
  3. Determine if the configuration utility is network accessible
    Check which addresses the BIG-IP configuration utility binds to using 'tmsh list sys httpd' or by reviewing network listener configurations
    Affected if The management web interface (typically ports 443, 8443) is accessible from untrusted networks (not localhost or strictly internal segmentation)
  4. Identify exposed modules
    Review installed modules via 'tmsh show sys module' and note which of these are enabled: Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, DNS, Edge Gateway, or Fraud Protection Service
    Affected if Any of the affected modules listed above are installed and the configuration utility is network-accessible

You are affected if F5 BIG-IP software is running with a version between 11.5.2 and 15.0.1 (inclusive) and the configuration utility web interface is network-accessible.

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 to a patched version of BIG-IP, BIG-IQ, iWorkflow, or Enterprise Manager as specified in F5's security advisory. Consider implementing DNS validation controls and network segmentation as compensating controls if immediate patching is not feasible.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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