Big Ip Advanced Firewall ManagerApplication · F5

CVE-2019-6657

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-01
Fix available
A fix is available. Upgrade to after 13.1.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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
On BIG-IP 13.1.0-13.1.3.1, 12.1.0-12.1.5, and 11.5.2-11.6.5.1, a reflected cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP Traffic Management User Interface (TMUI), also known as the BIG-IP Configuration utility.

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

Reflected cross-site scripting (XSS) vulnerability in an undisclosed page of the BIG-IP Traffic Management User Interface (TMUI). An attacker could inject malicious scripts via crafted URLs, which would be executed in the context of the victim's session when they access the vulnerable page.

MitigationApply the appropriate F5 BIG-IP hotfix or upgrade to a fixed version outside the affected ranges (13.1.0-13.1.3.1, 12.1.0-12.1.5, 11.5.2-11.6.5.1) as specified in the F5 security advisory.

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 Advanced Firewall ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip Local Traffic ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip AnalyticsApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip Access Policy ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip Edge GatewayWeb browser
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip Domain Name SystemApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check BIG-IP product version
    Run 'tmsh show sys version' via CLI or log into the web UI and navigate to Overview > Dashboard to view the software version
    Affected if The installed version falls within 11.5.2-11.6.5, 12.1.0-12.1.5, or 13.1.0-13.1.3
  2. Confirm the exposed module
    Identify which BIG-IP modules (AFM, LTM, AAM, Analytics, APM, Edge Gateway, DNS, or FPS) are licensed and running using 'tmsh show sys module' or the web UI at iControl > System > Software Management
    Affected if Any of the affected modules are licensed and active on a vulnerable version
  3. Verify TMUI accessibility
    Check if the Traffic Management User Interface is accessible on port 443 or the management port. Review network access lists or firewall rules to determine if TMUI URLs are reachable from untrusted networks
    Affected if TMUI is exposed to network segments where potential attackers could craft malicious URLs

The environment is affected if the BIG-IP version is within 11.5.2-11.6.5, 12.1.0-12.1.5, or 13.1.0-13.1.3 AND the TMUI interface is accessible to users who could be targeted with crafted XSS URLs.

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.3
Interim mitigation

Apply the appropriate F5 BIG-IP hotfix or upgrade to a fixed version outside the affected ranges (13.1.0-13.1.3.1, 12.1.0-12.1.5, 11.5.2-11.6.5.1) as specified in the F5 security advisory.

Fix this in Big Ip Advanced Firewall 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-6657 — 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-6657 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