Big Ip Access Policy ManagerApplication · F5
CVE-2019-6595
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 · uneditedCross-site scripting (XSS) vulnerability in F5 BIG-IP Access Policy Manager (APM) 11.5.x and 11.6.x Admin Web UI.
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 confidenceCross-site scripting (XSS) vulnerability in F5 BIG-IP Access Policy Manager Admin Web UI (versions 11.5.x and 11.6.x) allows injection of malicious scripts through unsanitized input that executes in the context of authenticated admin sessions.
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
>= 11.5.1, <= 11.6.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.0/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.
-
Verify BIG-IP APM versionUse the command 'tmsh show /sys version' or check the Admin Web UI under System > Software Management > RPM Summary to identify the installed APM version.Affected if The installed version falls within 11.5.1 through 11.6.3 inclusive.
-
Confirm Access Policy Manager module is provisionedRun 'tmsh list sys provision apm' or check System > Resource Provisioning in the Admin UI to verify if APM module is provisioned/enabled.Affected if APM is provisioned and running.
-
Verify Admin Web UI is accessibleAttempt to access the APM Admin Web UI at the management interface URL (commonly /my.policy or /apm) or check via 'tmsh list /apm profile access' to list active access profiles.Affected if The Admin Web UI is reachable and active.
-
Review APM access profile configurationsInspect access profiles via 'tmsh list /apm profile access' or through the Admin UI under Access Policy > Access Profiles to identify any custom scripts or unsanitized input fields.Affected if Custom input fields or scripts exist within APM profiles that could accept unsanitized user input.
You are affected if BIG-IP APM is provisioned with a version between 11.5.1 and 11.6.3 and the Admin Web UI is accessible, allowing potential injection of malicious scripts through unsanitized input fields.
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 dataUpgrade BIG-IP APM to a patched version beyond 11.6.x or apply F5 hotfixes; until then, minimize admin UI exposure and monitor for suspicious admin session activity.
Fix this in Big Ip Access Policy Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6595 — 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-6595 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