dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6591

MEDIUM · 5.4 CVSS v3.0 Published 2019-02-05
Fix available
A fix is available. Upgrade to after 14.0.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 APM 14.0.0 to 14.0.0.4, 13.0.0 to 13.1.1.3 and 12.1.0 to 12.1.3.7, a reflected cross-site scripting (XSS) vulnerability exists in the resource information page for authenticated users when a full webtop is configured on the BIG-IP APM system.

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 reflected cross-site scripting (XSS) vulnerability in BIG-IP APM's resource information page. An authenticated attacker can inject malicious JavaScript through the webtop resource page, which executes in the victim's browser when they visit a crafted URL. The attack requires the victim to have an active session and the full webtop feature to be configured.

MitigationUpgrade BIG-IP APM to a patched version (14.0.0.5+, 13.1.1.4+, or 12.1.3.8+) or disable the full webtop configuration if not required. As a temporary control, enforce strict Content Security Policy headers and sanitize user inputs in the resource information 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
Big Ip Access Policy ManagerApplication
Affected:>= 12.1.0, <= 12.1.3>= 13.0.0, <= 13.1.1.3>= 14.0.0, <= 14.0.0.4

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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. Verify BIG-IP APM is installed
    Log into the BIG-IP management console and navigate to System > Software Management > ISO Download or check the installed modules via tmsh: 'tmsh list sys module'
    Affected if APM module is not present on the system, the vulnerability does not apply
  2. Check the installed APM version
    Run 'tmsh show sys version' or check System > About > General in the GUI. Compare the version number to: 12.1.0-12.1.3, 13.0.0-13.1.1.3, or 14.0.0-14.0.0.4
    Affected if The version falls within any of the affected ranges listed, the system may be vulnerable
  3. Verify full webtop configuration exists
    In the BIG-IP GUI, navigate to Access Policy > Web Applications > Webtop or run 'tmsh list apm webtop webtop' to list any configured full webtop profiles
    Affected if A full webtop profile is configured and active, the attack surface for this XSS exists
  4. Inspect webtop resource page parameters
    Access the resource information page via the webtop and examine URL parameters. Look for unsanitized input reflection by testing with a benign string like '<script>alert(1)</script>' in the resource URL
    Affected if User-supplied input in the webtop resource page URL is reflected back without encoding, the system is vulnerable to reflected XSS
  5. Check for mitigating controls
    Review HTTP response headers on the APM portal for Content-Security-Policy headers or test if input sanitization is applied on the webtop resource page
    Affected if No CSP headers are enforced and inputs are not sanitized, exploitation is possible

The environment is affected if BIG-IP APM is running a version within the listed vulnerable ranges AND a full webtop configuration is active, allowing the reflected XSS in the resource information page to execute.

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

Upgrade BIG-IP APM to a patched version (14.0.0.5+, 13.1.1.4+, or 12.1.3.8+) or disable the full webtop configuration if not required. As a temporary control, enforce strict Content Security Policy headers and sanitize user inputs in the resource information page.

Fix this in Big Ip Access Policy 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-6591 — 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-6591 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