CVE-2019-6657
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 · uneditedOn 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 confidenceReflected 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.
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>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, <= 13.1.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check BIG-IP product versionRun 'tmsh show sys version' via CLI or log into the web UI and navigate to Overview > Dashboard to view the software versionAffected 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
-
Confirm the exposed moduleIdentify 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 ManagementAffected if Any of the affected modules are licensed and active on a vulnerable version
-
Verify TMUI accessibilityCheck 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 networksAffected 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.
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 dataApply 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.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6657 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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