Big Ip Access Policy ManagerApplication · F5

CVE-2019-6602

HIGH · 7.5 CVSS v3.0 Published 2019-03-28
Fix available
A fix is available. Upgrade to after 11.6.3 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
In BIG-IP 11.5.1-11.5.8 and 11.6.1-11.6.3, the Configuration Utility login page may not follow best security practices when handling a malicious request.

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 11.5.1-11.5.8 and 11.6.1-11.6.3, the Configuration Utility login page does not follow best security practices when handling malicious requests, resulting in a HIGH-severity vulnerability (CVSS 7.5) exploitable over the network against the web management interface.

MitigationApply the relevant F5 hotfix or upgrade to a patched version outside the affected ranges. If immediate patching is not feasible, restrict network access to the Configuration Utility using allow-lists or VPN-only access.

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.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip AnalyticsApplication
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip Application Security ManagerApplication
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip Domain Name SystemApplication
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.1, <= 11.5.8>= 11.6.1, <= 11.6.3

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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify F5 BIG-IP software version
    Run the command 'tmsh show sys version' or check the BIG-IP web UI footer which displays the version number
    Affected if The installed version falls within 11.5.1-11.5.8 or 11.6.1-11.6.3
  2. Confirm Configuration Utility is enabled
    Check if the web management interface is accessible by attempting to reach https://<management-ip>/ or run 'tmsh list sys httpd' to see the httpd configuration
    Affected if The Configuration Utility is exposed and accessible over the network
  3. Verify management access settings
    Run 'tmsh list sys management-ip all' to list all management IP addresses and their access settings, or check the BIG-IP GUI under Network > Management
    Affected if The management interface is bound to a routable IP address rather than localhost only
  4. Check if any hotfixes are applied
    Run 'tmsh show sys software' or check the output of 'f5curl /tm/shared/resolver/node' for installed hotfix information
    Affected if No relevant hotfixes for CVE-2019-6602 have been installed

The environment is affected if the F5 BIG-IP version is 11.5.1-11.5.8 or 11.6.1-11.6.3 AND the Configuration Utility web management interface is accessible over the network.

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

Apply the relevant F5 hotfix or upgrade to a patched version outside the affected ranges. If immediate patching is not feasible, restrict network access to the Configuration Utility using allow-lists or VPN-only access.

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-6602 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-6602 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